I have recently upgraded a test instance of Orchestrator at a client from v2018.2 to 2019.10. The upgrade appears to have mostly gone well, however in the course of testing I have discovered that I cannot run jobs from Orchestrator. I am able to run the same process from the Agent, but when I try to run from Orchestrator the job gets stuck as ‘Pending’ and never starts.
I have reviewed other topics on the forum but unfortunately the solutions do not seem to apply. The robot type is ‘Non-Production’ (not studio) and the domain\username format is correct (the same machine has been provisioned with the production Orchestrator instance using the same domain\username format), the credentials are correct and the robot is connected and licenced.
Any assistance on this would be appreciated.