I’m facing an issue trying to do Lesson Orchestrator 2018.3 - Practice 3 in which i have to create a job in Orchestrator. When i try to create it, i cannot find any robot.
After some test and troubleshooting, i realized than ‘Studio’ Type robot can not run processes from orchestrator any more and now i must use an ‘unattended’ robot.
I create it now, and it can be selectable from “create job”, but after that, job still has a “pending” status and it doesn’t execute.
I tried to restart application, delete environment, robot, and even complete Service, but Job doesn’t execute properly.
1 VM with studio installed and connected as type: Studio
1 VM with only the robot installed and connected as type: Unattended
I develop on the studio, publish my packages to Orchestrator. I test FROM studio on studio, but not from orchestrator > studio. That is where the robots are for.
It is making things a lot easier when you are testing/learning.
The workaround would be what you also did:
Orchestrator: Change the robot type to Unattended. Change the setting for your robot: (Login to console: Yes)
Studio: disconnect the robot and reconnect it. Sometimes wait a couple of minutes to let things sync.
Orchestrator: refresh orchestrator and you should be able to start a job. Keep your studio machine logged in.
If your job is not starting, check the robot logs if you something there.
C:\Users\Alberto_VR\AppData\Local\UiPath\Logs
Solution to unlicensed/licensed robot:
Going to user → check “unattended” robots, disable one (system creates two unattended robots due some bug), then, take your robot, change type from ‘unattended’ to ‘attended’ and change it again to ‘unattended’.