We have a process that need to run every 30 mins but if one execution is in running state this time based trigger is not required to create another job. Processes can start in any of our Prod VMs and not the same robot every time. Can this be done within orchestrator by any settings and not from code?
Similar exists in Queue based trigger where you can set maximum number of running jobs.
Hi @SnehajitDas
Yes, this can be handled in Orchestrator without code.
When creating the Queue Trigger, enable the option:
“Do not allow trigger to start a new job if the previous one is still running”
This prevents overlapping jobs, even if the process runs on different robots or machines.
Ensure you’re using Modern Folders and robots are correctly configured.
If you found helpful please mark as a solution. Thanks
Happy Automation with UiPath
@UiPath_Community still looking for an answer
Hi @SnehajitDas
Sorry for the misunderstanding , In Time-Based Triggers, this option is not available by default in Orchestrator.
This control is only available in queue-based triggers:
