I have one process with multiple queues that all have triggers. I raun a process which is feeding all queues in the same time.
Right now when items are added multiple jobs are started. at least one per queue.
I like to restrict the maximum numbers of running jobs for the same Process to 2 in order not to block the activity of other processes.
I run Orchestrator Cloud. I remember that in Orchestrator on Premises we can chouse the type of evaluation but on Cloud this function is not available.
How can I restrict to only run 2 Jobs per Process not 2 per Queue.
As far as I know, this isn’t configurable in Automation Cloud. The maximum concurrent jobs are evaluated per queue trigger, not per process.
As a workaround, you can assign only 2 unattended robot licenses to the folder where this process runs, which effectively limits concurrent executions. Alternatively, implement logic in the bot to check the number of currently running jobs for the same process, and if the count is already 2, stop/exit the new job gracefully.
You can also try configuring the maximum concurrent jobs at the Queue Trigger level. Since all triggers reference the same process, it may prevent more than two jobs from running concurrently, depending on your configuration.
If I implement inside the automation to check if an additional one is running I already ocupied the machine and it will keep it ocupied just to check.
The limit on the machines is also not 100% viable since we might vave mahines which are free but the process will not start even if is in the limit of 2 because some other processes are running on the machines selected.
I don’t understand why in an evoluated platforms basic and usefull settings were removed.
Also anothe missing functionality for example is to limit the Queue triggers to only fire in specific timeframes.