Add delays to a workflow
Pause a workflow for a duration or until a future date. Waiting runs are stored and later resumed by Kanopee while other runs continue independently.
Delay for a duration
The Delay for action supports days, hours and minutes.
The total duration must be greater than zero. The action also exposes a business-days option for the day component, where the current implementation skips weekends for that day calculation.
Use a duration delay when the wait should be relative to when each record reaches the step.
Delay until a future date
The Delay until date action stores a fixed target date/time and timezone.
The selected target must be in the future when the workflow is configured/published.
Use this option when all matching runs should wait until a specific date rather than wait for a relative duration.
What happens while a run is waiting
When a workflow reaches a delay, Kanopee does not block the rest of the system.
That individual run is saved in a waiting state and Kanopee schedules work to resume it later. Other records and workflows continue independently.
When the wait ends, the run resumes from the step after the delay.
If you edit the workflow during a delay
Kanopee records the workflow version when a record enrolls.
If you edit and publish a new version while an older run is waiting, that waiting run continues using its original published version.
New enrollments use the newer published version after you update the workflow.
If you turn the workflow off
Turning a workflow off is different from merely editing it.
If a delayed run is due to resume but the workflow has been disabled, the runtime checks the workflow state and skips the continuation.
Turn the workflow back on for future matching, but do not assume a run already skipped while it was off will automatically replay.
If a delayed run does not resume
If a delay appears stuck:
- confirm the workflow is still active
- recheck the configured duration or target date
- check timezone for fixed-date waits
- review the Enrollment view for the run's state
- remember that disabling a workflow can cause a due delayed run to be skipped.
If the run should have resumed and configuration is correct, support may need to inspect the scheduled-job/runtime state.
---