Issue in Triggering orchestrator Job with API Call

Hi All,

currently we are facing some issue in triggering orchestrator job using API.I would say its working but whenever we tried to deviate it to another machine it’s still redirecting to specific machine. To give a detail explanation about the issue, we have a custom-made activity to trigger API calls. So, we are using this activity inside a dispatcher bot to trigger performer automatically. So, we have to pass the Orchestrator folder name, Bot name (Machine Name) in which we want to trigger the performer bot. It was working very fine in classic folders recently upgraded to modern folders. Since then, its running in only one machine if we provide other machine details still not its triggering in specified machine. Can anyone help me regarding this?

As per my understanding once you better try this once
I think it works
thanks


Try to enable it

Hi Usha,

can you elaborate what has to be done here!

Why aren’t you just using queues? Usually you have your dispatcher put items into a queue, and then a queue trigger starts the performer.