Hi Christian,
I know this isn't what you're going to want to hear/see. But the 'execute missed schedules' feature only runs when Scheduler first starts up, which I imagine is only when the Blue Prism Server service is starting up. So, even though the way you're wanting it to work is intuitive, it's specifically for schedules that were missed while the server was not running.
Here's an excerpt from the System Manager documentation in Blue Prism:
When the scheduler initialises, it can check back for recent schedules which should have executed while the scheduler was not running.
To configure how far back the scheduler should check, the number of minutes to look back can be entered in the 'Execute missed schedules from the past n minutes' text box.
To set the scheduler to not look back at all, a value of 0 (zero) should be entered.
Note that if a schedule is discovered which should have executed multiple times in the configured period, it will only be executed once. Equally, schedules which have successfully run will not be executed again.
Also note that this setting is only effective when the scheduler is starting up, so it will have no effect on a running scheduler.
To accomplish what you're looking for, you could consider Dynamic Scheduling. In your case though, with only 2 licenses, you would almost certainly want to set up a script that runs outside of Blue Prism (not consuming a license) that would start up Blue Prism process sessions by CLI commands. I've seen a few people on this forum who have done this in production. I've only done this for testing and funsies, but I've never had a requirement for it in prod.
Maybe amibarret will respond with his solution. He's described it before on other posts, but I don't have the link that post right now.
Dave
Respectfully,
Dave
Dave Morris
3Ci at Southern Company
Atlanta, GA
