yes, we are using Orchestrator and I know of the cron expressions.
Problem is that cron tells the process when to start, not when to stop.
Short example, if I have a process with a queue of 1000 cases and I can allocate it just 2 hours per day, if I use cron expression it will tell the process to start between the 2 hours, but it won’t stop when they are done if he hasn’t completed all the cases.
What we will do for now will be to implement a time-check in the script and stop the process when it’s time has come
Source of requirement: one client has just one license and multiple business areas to make happy per day, meaning more processes to run within a limited timeframe