Possible to prevent same process triggering again before the previous run is finished when there's multiple unattedned robots?

Let’s say I have 2 unattended robot on 2 machines and some triggers setup, is there a way to prevent the scenario where the same trigger/process running on both machine simultaneously?

Trigger A is scheduled to run every 10 mintues.
2 unattended robot setup on PC X and Y.

What I am trying to prevent:
Process a triggers and runs on PC X which will takes 30 minutes to run.
After 10 mintues, process A triggers again and added into the job’s queue.
Process A runes on PC Y when PC X haven’t finish running.


Hello @puff

Does that mean you have dynamically allocated 2 robots to execute the process and whenever which robot is free it will start the execution? Is that the scenario?

Or you have scheduled the process in both the robots separately?


The process is set to dynamically allocated. But I would lke to stop it from running simultaneously on different robots at the same time. So the process is still dynamically allocated but only triggers when the previous one has finished.


If you don’t want it running at the same time why do you have it set up to be able to do that?

How do I setup a schedule so a process will dynamically assign to a free robot but don’t allow it to run simultaneously?

Or in other words, how to setup a schedule that won’t be triggered until the previous triggered process from the same schedule has finish running.

Specify the robot under which it runs. Don’t let it choose.

But I’d like the process to dynamically run on any of the robot, so even if let’s say robot 1 is busy running something else, the scheduled process can still run on robot 2.

Just that the same process must only have maximum of 1 robot running it at any given time.

Your requirements conflict, then. You want two things that are contradictory. Unfortunately, only Queue Triggers allow you to set how many Jobs can run at one time. I don’t know why. Seems like an oversight by UiPath.

Appreciate the help, seems the easiest way out is to just allocated the process to specific robot seperately.

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.