Latest Feature

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 vs. Published: Edit freely in Draft; create temporary runs to test your changes.
• Users continue to use the Published version
• 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. Edit the workflow (changes save to Draft).
2. Test the workflow by creating private runs, only seen by other admins.
3. Publish to create a new version.
4. If needed, restore a prior version.

Best practices

• Use Drafts for testing before going live.
• Add clear publish notes so teammates know what changed.
• Review version history regularly for policy alignment.