Unattended Robot Config Issue

Help Robot
, ,
1

Hi All,

I hope you are doing well.

Please find the attached screenshots for your reference regarding this issue.

We have completed the following troubleshooting steps:

  1. Robot has been created and connected to all relevant folders. The appropriate roles have been assigned.
  2. Domain, username, and password were correctly entered during robot setup.
  3. Machine has been created and licenses have been allocated properly.
  4. UiPath Robot has been installed and configured with the correct Machine Key, Orchestrator URL, and Machine ID.
  5. Robot is allocated and license appears as connected on the virtual machine.

Issue:

  • The process runs successfully when triggered from UiPath Assistant (Attended mode).
  • However, when we run the same job via Orchestrator in Unattended mode, it fails (job is faulted).

We suspect there may be an issue with Unattended runtime or machine configuration, though everything appears correctly set.

I tried multiple ways it’s not working can you please help me on this.

Looking forward to your assistance.

Screenshot 2025-08-25 202832
Screenshot 2025-08-25 202832760×473 175 KB

Thanks,

Kalai

2

Pls Check and try below point - Check Orchestrator → Users → Robot settings → verify username/password.

Make sure Unattended runtime is allocated.

Configure Resolution & Login to Console = No in Machine settings.

Review the Job logs in Orchestrator → it will show whether the failure is at login or during execution.

3

Go to Orchestrator → Tenant → Users find the robot account and edit → Under Unattended Robot Settings, re-enter the Domain\Username and Windows password. Even if you entered before, retype the password because sometimes it’s blank or incorrect.

Cheers

4

Hi @kalaisan93

Pls check below link:

Happy Automation

5

Try these before trying to start a new unattended job from Orchestrator:

  • Login manually to the VM of the robot via RDP and check if the credentials provided in Orchestrator are the same. If not, correct them in Orchestrator.

  • Add the robot user EAD\C280500 in the Remote Desktop Users group at Computer Management -> Local users and Groups -> Groups

Add for the Remote Desktop User group in Group Policy Management Console (gpmc.msc ) these permissions:

Allow log on locally
Allow log on through Remote Desktop Services
Access this computer from the network

  • Try to create a new machine template with 1 unattended runtime and make sure that that license is not used by another robot.

Add the machine template to the Orchestrator folder where the robot is present.

Disconnect the robot from the old machine template, and connect it back to Orchestrator using the Client ID connection in Assistant with the new machine template details (Client ID and Client Secret).