Hey @razia
This usually indicates that:
- Orchestrator can’t find an available robot/machine to assign the job to.
- The job sits in a Pending queue, waiting for a machine with the right config (user + robot) to become available.
- UiPath Assistant works because it’s running in attended mode, directly on a known machine with a connected robot session.
Checklist to resolve “Pending” jobs in Orchestrator
- Verify Machine Template / Machine Key Mapping
Go to Orchestrator > Tenant > Machines:
- Make sure your machine (or machine template) is properly assigned.
- If using Manual Machines (non-template), ensure the machine name in Orchestrator matches exactly (case-sensitive) the name of your VM.
- If using Machine Templates, make sure your VM uses Modern folder and the Machine Template key.
- Check Robot/User Mapping in the Folder
In the folder where the jobs are stuck:
- Go to Folder > Users
- Confirm that the robot user (the Windows user that should run the job) is:
- Added to the folder
- Has “Unattended Robot” role
- Has a correct Robot configuration (i.e., mapped to the right machine, and with the correct domain\username)
Tip: Check this under Tenant > Users > Robot Settings — you should have a valid entry for DOMAIN\Username, resolution, login details, etc.
- Machine is online & licensed
- Go to Orchestrator > Monitoring > Machines
- Confirm that the machine is available, licensed, and shows heartbeats.
- If the robot is not connected properly, jobs won’t get assigned.
- Make sure Interactive Sign-in is enabled (if Modern robot)
If you’re using Modern Folders with unattended robots:
- The robot must have interactive sign-in enabled.
- In Robot Settings, verify:
- Username is in
DOMAIN\Usernameformat - Windows password is set (this is required for unattended login)
- “Automatically create a Windows session” is checked
- Username is in
these steps is generated by using chatgpt… but you can try these steps .
cheers