Workflow Steps
Delay
A Delay step pauses the run before continuing to the next step.
Duration options:
Fixed time — wait a set number of minutes, hours, or days.
Until a date field — wait until an available stored date on the run’s record, such as a
subscription’s end date. Set Offset days to run before or after that date: negative numbers
run before it, positive numbers run after it, and zero uses the date itself.
The date and offset are read when the run enters this Delay step. Editing the record afterwards
does not move an already scheduled delay. Check the saved settings before publishing.
Execution window (optional):
After the delay elapses, choose a Time of day and allowed Days of week, in your school’s
timezone. This is a chosen resume time, not a start-to-end office-hours range. When first enabled,
the editor suggests 9am Monday to Friday. With no days selected, any day is allowed.
Re-check trigger condition:
New delays have Recheck trigger on. When the delay finishes:
Condition Becomes True and filtered Recurring Schedule runs continue only if the
record still matches the original filter.
Condition Stops Being True runs continue only if the record still does not match
the original filter. If it matches again, the run is cancelled.
This is usually the right behavior — for example, a “your subscription is expiring” reminder shouldn’t fire if the member already renewed during the delay.
Missing or deleted records do not pass these checks. Manual, event, and date-field triggers
do not perform a filter check here.
Turning re-checking off does not bypass a workflow-level exit condition.
If you have a long delay (several days) inside a condition-triggered workflow, re-checking is your safety net against sending stale messages.

Search terms: