Unattended job stuck in Pending — machine credential mismatch error

Help Orchestrator
1

My unattended jobs are stuck in “Pending” state permanently.

Error shown in Orchestrator:
“The unattended robot has the wrong machine credentials to execute
the job (the username of the machine is not the same as the
username in the user credentials)”

What I’ve tried:

  1. Checked UiPath Assistant - it shows connected to my Labs tenant
  2. Tried “Run As Myself (Personal automation)” account setting
  3. Ran “whoami” and confirmed my Windows username

None of these resolved it. The job (PharmaSignal_CaseTrigger)
just sits in Pending and never starts execution.

image

image
image833×691 61.9 KB

image
image1228×845 76.7 KB

Could someone help me check if my Labs tenant machine/robot
configuration is set up correctly? Happy to share screenshots
or a screen-share if needed.

Thanks!

2

You are showing completely two different robot users. One is a robot account with no UI profile, and another with UI profile but is not an unattended robot → will not work.

If you need to run as the unattended robot:

  • Make sure that at least one unattended runtime is available for the robot to run.

  • Make sure that the robot is installed in Service Mode. If you see the UiPath Robot service in the services.msc, that means is installed in service mode.

  • In the robot machine, make sure that the robot is connected to Orchestrator using Client ID connection.

  • In the Start job in Orchestrator do not select Run As Myself, but select the Machine Template, the unattended robot username and the Hostname and only after that start it.

3

3 things you need to check..

  1. unattended license availability.
  2. whether the machine is configured with unattended setup.
  3. check what kind if UiPath robot service is running on your target machine.

your host identity and windows username seem to mismatch so, this is to be sorted too.

SG.