Error when running process from Orchestrator

[andrzej.kniola (Andrzej Knioła)]

Usual Orchestrator errors (FAQ) - Troubleshooting

This is a list of errors that usually occur in Orchestrator and cause the Robot to not start a job. These errors can be found in the Jobs page, in the Job Details window. No robot available for user X This error is displayed when the Robot provisioned on Orchestrator has a username does not coincide with the Robot machine’s username. Permission missing: Launcher This error is received in the following scenario: robot is connected to orchestrator with user “abc” on the robot machine you try…

Check the “specified logon session does not exist it may already have been terminated” part.