I have a scenario where I want to run a process simultaneously on 3 different user accounts, but I want to make sure it does not run on more than 4 machines at the same time
Hey @Rahul_Rajendran,
Time triggers in UiPath don’t natively support limiting concurrent executions like queue triggers. Instead, you can use the Job Count Strategy setting:
Set it to PerProcess so that the trigger only queues as many jobs as needed to reach your maximum (4), accounting for currently pending/running jobs.
Ensure “Allocate Dynamically” is used for execution targeting so jobs queue properly and aren’t launched immediately if robots are busy.
For more details:
If the trigger in only once a day or limited then have 3 time triggers which triggers 3 jobs only
If the trigger is multiple times and if one is running then you dont want others to run..one way you can again acheive is to set time trigger alpng with account machine mapping ..so that as another job is running on same combination one more job would go to pending till this completes..so you still would have only 3 jobs running at any given point
Cheers
As per my knowledge, to limit runs across machines, create a shared counter in a database or file that tracks active jobs. each job checks this counter at start. If the count is below 4, it increments and proceeds. If 4 or more, the job waits or stops. When a job finishes, it decrements the counter. This controls max simultaneous runs across all machines.
time triggers have no built-in concurrency limit.
Orchestrator - Time triggers
If helpful, mark as solution. Happy automation with UiPath
In your case, you want to run a trigger on multiple machines but limit it to 3. While setting up the time-based trigger, go to the “Execution Target” section and use the “Select valid account-machine mapping” option. There, you can add 3 specific machines to run the job. This setup ensures that the job will always run on those selected 3 machines.
