Workflow Versioning

Make changes in a private Draft, keep a stable Published version for your team, and maintain a full version history with restore. Runs are always created from the published workflow.

How it works

• Draft Version vs. Published: Edit freely in Draft; create temporary runs to test your changes.
• Users continue to use the Published Workflow
• Version History: Each publish creates a new version with who/what/when, plus one-click restore for rollback.
• Audit & Compliance: Transparent change tracking builds an audit trail and team confidence.

Typical flow

1. Create a new version of the workflow (changes save to Draft).
2. Test the workflow version by creating runs, only seen by other admins.
3. Once fully tested, publish the version as the new live workflow.
4. If needed, restore a prior version.