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.