Beginner4 min
Draft vs Published
Workflows have two states: Draft (work in progress) and Published (live). This separation lets you make changes safely without affecting running workflows.
Understanding Versions
Draft Version
- Your working copy
- Editable at any time
- Used for testing
- Not triggered by real events
Published Version
- The live, active version
- Responds to real triggers
- Immutable (can't be directly edited)
- Replaced when you publish a new draft
The Workflow Lifecycle
Create → Edit Draft → Test → Publish → Live
↓
Make Changes → Test → Publish → Updated Live
Working with Drafts
Creating a Workflow
New workflows start as drafts:
- Click New Workflow
- Build your workflow
- Test using manual execution
- Publish when ready
Editing an Existing Workflow
Changes go to the draft:
- Open your workflow
- Make edits on the canvas
- Changes auto-save to draft
- Published version unchanged
Testing Drafts
Test your draft before publishing:
- Click Test in the toolbar
- Provide test data
- Verify behavior
- Fix any issues
Publishing
When to Publish
Publish when:
- Testing passes
- Changes are ready for production
- You want to activate a new workflow
How to Publish
- Open your workflow
- Click Publish in the toolbar
- Review the changes summary
- Confirm publish
What Happens
- Draft becomes the new published version
- Previous published version is replaced
- Live triggers now use new version
- Draft resets to match published
Version History
View previous versions:
- Open your workflow
- Click Version History
- See all published versions
- Compare changes between versions
Rollback
Revert to a previous version:
- Find the version to restore
- Click Restore
- Version becomes new draft
- Test, then publish
Active vs Inactive
Separate from draft/published:
Active
- Workflow responds to triggers
- Executions are logged
- Counts toward limits
Inactive
- Workflow is paused
- No trigger response
- Good for maintenance
Toggle in workflow settings or dashboard.
Best Practices
1. Always Test Before Publishing
- Use manual execution
- Test edge cases
- Verify all branches
2. Use Meaningful Publish Messages
When publishing, add a note:
- "Added email notifications"
- "Fixed date formatting bug"
- "Updated API endpoint"
3. Review Changes
Before publishing:
- Check the diff view
- Verify intended changes
- Confirm nothing unexpected
4. Monitor After Publishing
After a publish:
- Watch execution logs
- Check for errors
- Verify expected behavior
Common Questions
Can I edit the published version directly?
No. Edit the draft, then publish.
What if I need to make an urgent fix?
Edit the draft, test quickly, then publish. The published version updates immediately.
How long is version history kept?
Based on your plan:
- Free: 5 versions
- Pro: 30 versions
- Enterprise: Unlimited
Can multiple people edit a draft?
Yes, but changes may conflict. Coordinate with your team.
Next Steps
- Sharing and Permissions - Collaborate
- Execution Logs - Monitor runs
- Debugging Errors - Fix issues
Tags
workflowsversioningpublishing