Start Job activity question

[Jarzzz (Kyle)]

Hey All,

Question for the community… I’m attempting to use the “Start Job” activity found under Orchestrator - Jobs. It’s set up and starting the job as expected. My main questions is the, documentation leads me to to believe there is a way to start the new Job on the Robot running the process.

“Enables you to start a job on Orchestrator on a specified number of Robots. … The activity runs under the Robot which executes it.”

Start Job

When I run the process containing the “Start Job” activity, the process found in “ProcessName” of the “Start Job” properties panel starts on a random available robot. How does one set the process to run on a specific robot (I want the next Job to to start after first job finishes, on the same robot).

[bcorrea (Bruno Correa)]

This activity is quite limited on that, you would need to use the Orchestrator API for that…

[Jarzzz (Kyle)]

Ahh, was hoping there was some secret sauce.

I wont go in that depth, ill just create some schedules to execute a few seconds after one another.

Congrats on the Community Moderator! @bcorrea

[Jarzzz (Kyle)]

@bcorrea To share some new knowledge… Just did some research on this and found this thread. A user made the suggestion to create a separate environment for the process with only the robot desired having access to that environment. Brilliant!

'StartJob' activity starts job at wrong robot

Hey, The StartJob activity doesn’t trigger a process on a specific robot. This activity can be used to randomly trigger one or multiple bots coherently. The other option you can use is triggering via API calls and starting job based on robot ID, In this case, you have to Authenticate via API first, get the release key, find/get sessions, get the robotID and trigger process based on robotID. Here is a reference link. (Multiple reference links inside it with more information) Hope this help…

[bcorrea (Bruno Correa)]

nice, we have a very content rich Forum here

[Jarzzz (Kyle)]

That we do!

Cheers