Is there a best practice re canceling a scheduled API WF as soon as the Only When criteria isn't met?


For scheduled API WFs with Only When criteria, if an event occurs such that the criteria isn’t met, the scheduled API WF can either stay in the Scheduler and not run on the scheduled date or can be cancelled before the scheduled date. Is there a reason to cancel the scheduled API WF in this scenario?

For example, an API WF is scheduled to run on a certain date only if a field is empty. If an event results in the field not being empty, is there any dis/advantage to leaving it in vs. removing it from the Scheduler?

Many thanks

I mean…if you are a methodical and extremely organized guy, you will have to deal with your scheduler full of events that will never be triggered :sweat_smile:

1 Like

No, none at all.