We have a process that is running constantly on our bot license, but there are other process that also needs to run on this license.
How does a job with Critical Priority work when there is a process running 24/7? From my understanding it should finish the current transaction on the constant process, then run the Critical Process, and then continue with the rest of the transactions on the constant process. Or is this not how it works? If not, how can we set it up so that it acts in this way?
From documentation (Orchestrator - About Jobs - https://docs.uipath.com/):
If you configure a job to execute the same process multiple times, a job entry is created for each execution. The jobs are ordered based on their priority and creation time, with higher priority, older jobs being placed first in line. As soon as a robot becomes available, it executes the next job in line. Until then, the jobs remain in a pending state.
If you have just one Unattended runtime occupied by a 24/7 job, the Critical priority job doesn’t get a chance to get started. One possible solution is to change the 24/7 job to be triggered by a Time Trigger by certain intervals with maybe a Stop After specified (so that it will stop even if there are queue items to be processed).