I’m facing an issue with Orchestrator — processes are not starting (they get stuck in a “Pending” state), whether triggered manually or via a schedule. However, when I run the same processes through UiPath Assistant, everything works fine.
I also noticed that in the folders where the processes are stuck, the Monitoring tab shows them as Pending, but they do not appear in the Jobs tab.
Hey @razia
It seems like your issue is related to the machine allocation or unattended robot configuration in Orchestrator. First, make sure the user assigned to the folder has an unattended robot provisioned correctly with the domain\username and password filled in. Also, confirm that the machine you’re using is connected and assigned to the right folder in Orchestrator. If there are no available unattended licenses, the job will stay stuck in “Pending”, so it’s worth verifying your license availability too.
You appear to have a filter on, this is likely stopping you from seeing the job thats in a pending state.
Firstly check those filters and remove them so you can see the job.
Can you explain how you create the job? Usually if there is a missing robot account or machine template in a folder you cannot create the job, so I would assume that works but some more detail there is useful.
After that, as suggested, its likely there is an issue where the executor cannot log in to the machine with the credentials provided, this unfortunately doesn’t give a very good alert / error in the Orchestrator in my opinion, but would mean you could create a job, but it never starts.
Have you been able to run unattended jobs on this machine / robot before in any other folder or is this the first one?
One more common cause:
if you performed your client installation without activating the robot as service component, the Orchestrator is not able to start a robot on that machine if there is no active user session. This would explain why running with assistant works (so there is an authorized connection, folder access etc.) but not standalone.
To solve this, run your studio installer again, modify it by adding the robot service option. No worries, all of your other settings are maintained.
After the instalation sign off the user on the client and the machine should be available in the orchestrator for a run.
yes i know but the steps is correct thats need to be check .. because the issue is being caused related to Robot or Machine did not setup properly.or not being assigned to that particular folder.where bot need to be run
Its not a problem to use a GPT, but the forum guidelines request you respect the rest of us and make it clear in your post that it was written by a GPT, please try to do that in the future.
is unattended robot and machine assigned to the folder you are trying to run the process from?
when you try to start a job manually, do you see any robot account or machine showing up there in respective drop downs?
if step 1 and 2 are fine, please ensure your machine is not in maintenance mode. to check go to → tenant-> monitoring-> unattended session ->toggle maintenance for your machine.
