I am experiencing a delay in starting a job using the platform.uipath.com orchestrator. I’m using the API to start a specific process on a specific robot and sometimes there is a 10-15 seconds delay between the time the job appears in the orchestrator, and shows as “Pending” and the time the robot starts working on it when it changes to “Running”. It’s worth mentioning that when I do this through an orchestrator that we host, the job always starts with very little delay 1-3 seconds. Is this an intended behavior for the cloud platform?
I’ve seen on the forum that some people mentioned this delay a while ago, but for them, the 15 seconds was too soon and they wanted to increase it. In our scenario, in which the job is triggered by a message from the user in a chat interface, it needs to start ASAP.
I can provide more details about the setup if it helps, but I wanted to first see if this rings any bell. Maybe I’m missing something easy, like a setting somewhere.