How Workflows Work
Trigger re-checking
Many triggers are condition-based — they fire when something becomes true (for example, “member’s subscription is expiring”). Once the trigger fires and the run starts, Kanri can optionally re-check that condition again later.
New Delay steps have Recheck trigger on. For Condition Becomes True and filtered
Recurring Schedule workflows, this checks the original filter again when the delay finishes.
If the record no longer matches, the run is cancelled instead of continuing.
Manual, action-event, and date-field triggers do not gain an extra eligibility check from this
switch. An event-triggered welcome message does not expire simply because the event happened
several days ago.
For Condition Stops Being True, the record must still not match the original filter.
If it matches again, the run is cancelled. Missing or deleted records do not pass a condition
or recurring-filter re-check.

Search terms: