uses Dynamic Allocation so that it can use whichever Robot that is available at the moment
can take more than an hour to complete
wasn’t designed to handle multiple job runs in parallel
Question is:
Is it possible to limit the number of simultaneous job runs for that particular process so that there will never be a chance for it to run twice at the same time?
A Queue Trigger is the only known to me way to handle this case, but I’d like to keep using a simple Time Trigger.
To address the issue of preventing multiple jobs from running simultaneously, it’s important to understand that a Queue Trigger is ideally suited for this. However, if you prefer to continue using a Time Trigger, you can consider adjusting the schedule to ensure that the process completes before triggering a new job.
You can modify the Time Trigger to a schedule that accommodates the longest possible execution time. For instance, if the job may take up to 1.5 hours, schedule the Time Trigger to run every 2 hours instead of every hour.
Other process job runs can impact the time at which my process will run, meaning if I schedule it to run at 15:00 there is always a chance that it will actually start at 15:59 (and then at 16:00 if I want to run it every hour), as such your proposed solution is unfortunately not bullet proof.
Yes, that’s inevitable. If the bot is time critical, it would be good idea to have a separate runtime for it otherwise even if we mange to avoid concurrent run, there will be always chance that it misses the desired run time.