I the SF you can define multiple schedules for 1 system flow. F.e. 1 runs every day at 00:01 and 1 runs every hour on 04:00.
However you’re able to define 2 schedules, only 1 schedule can be active.
I would suggest the idea to have multiple schedules active. Of course it’ll need some checks to prevent running them on the same moment, but that should be doable.
+10We are running into the same limitation.
Our use case requires a system flow to run every 20 minutes during working hours, while outside working hours it needs to run once per night.
Running the flow continuously during the night is unnecessary from both a durability and server capacity perspective, so having multiple active schedules for a single system flow would be very useful in this scenario.
+12I don’t expect us to implement this soon. Would adding a Decision process action right after the Start action, with some logic in it to determine whether or not the System flow should continue, suffice for your Use Cases?
Process flow actions | Thinkwise Documentation
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
