How Workflows Work
Exit conditions
Trigger re-checking only re-evaluates the original trigger condition, and only when a Delay step finishes. Sometimes you need something broader: a way to stop a run early if any unrelated condition becomes true, checked continuously throughout the run, not just at delays.
That’s what an exit condition is for. It’s a single filter you set once for the whole workflow (separate from the trigger and from any individual step). Kanri checks it right before every step runs — not only after delays — and if the record matches, the run is cancelled immediately with no further steps executed.
For example, a reminder workflow could have an exit condition that matches a record no longer
needing follow-up. Kanri checks it before the next step executes, including when a delay resumes.
It does not interrupt an action already executing or continuously monitor a sleeping delay.
Exit conditions are optional — leave them unset and a run will only stop for the reasons covered above (reaching a step with no next step, a re-checked trigger condition no longer being true, or the workflow being disabled or deleted).
See Building in the Editor for how to set one up.

Search terms: