Versioning in Stripe Workflows: Ship workflow changes with confidence

Summary

Stripe Workflows previously required teams to edit live workflow definitions directly, leaving no draft state, historical definitions, straightforward rollback, or reliable way to inspect which configuration shaped an older run. Versioning addresses this with a dedicated draft for iteration, immutable numbered published versions, and version history that can include descriptions, authors, status, and run counts. Publishing creates a complete snapshot containing steps, branches, conditions, variable references, calls, and configuration; new runs use it immediately, while in-progress runs finish on the version they started with. Each run records its exact version and exposes the workflow definition, including taken and untaken branches, while a past version can seed a new draft for rollback; versioning is available in Stripe Workflows, where new workflows include a draft by default.

Takeaways

1. 1

   Drafts let teams add steps, branches, conditions, messages, or other logic without affecting the active production version until publication.

2. 2

   Published versions are immutable snapshots. New runs use the newly published version immediately, while in-progress runs finish on the version they started on.

3. 3

   Each run records its workflow version, allowing inspection of the definition and both taken and untaken branches; a known version can also support rollback.