Version History
How versioning protects in-progress runs
When you publish a new version of a workflow, in-progress runs are not affected. Each run is pinned to the version that was active when the run started.
Example: A member is in the middle of a 3-day delay step in v2 of your “Renewal Reminder” workflow. You make changes and publish v3. The member’s run stays on v2 — it finishes with the v2 logic. New runs created after the publish use v3.
This means you can safely update a workflow at any time without disrupting members who are mid-run.
Versioning freezes the workflow definition, not every record it uses. Actions can read current
member details and the current content of a selected message template when they execute.
Changing those records can affect a later step even when the run stays on an older workflow
version. Disabling or deleting the workflow cancels in-progress runs.

Search terms: