Keeping your journey workflows up to date is important, but sometimes you need to look back.
With Versioning, you can view your journey’s publish history, review previous versions, and restore an earlier version if needed.
Whether you want to double-check what changed, troubleshoot an issue, or roll back to a previous setup, Versioning makes it simple and safe.
What is Versioning?
Every time you publish a journey workflow, we save a version of it.
With this new feature you now can:
🕒 Review your publish history
👀 Preview what changed
🔁 Restore an older version
🛟 Safely revert if something isn’t working as expected
Think of it as a “save history” for your journey.
How to View Your Version History
You can access version history directly inside your journey builder.
Step 1 -> Click on the three dot options in the top right corner
Step 2 -> Open Version History
Click on the Version history button.
You’ll see a list of all previously published versions, including:
Version name
Date & time published
Who published it
Number of actions in that version
Which version is currently in use
How to Review Changes Between Versions
Want to know what changed?
Step 1: Click the three-dot menu next to a version
Step 2: Select Compare versions
You’ll see a clear summary of changes, including:
✅ Actions added
🔄 Actions modified
❌ Actions removed
This makes it easy to understand:
What was updated
What was removed
What was newly added
No technical knowledge required, everything is clearly grouped for you.
How to Restore a Previous Version
If you’d like to go back to an older version:
Step 1 -> Open Version history
Step 2 -> Click the three-dot menu next to the version OR click on the "Restore this version" when previewing the version you are looking to restore to
Step 3 -> Select "Restore this version"
Once restored:
That version becomes your active draft
You can review it before publishing
You can make further edits if needed
You’re always in control.
When Should You Use Versioning?
Versioning is especially helpful when:
A workflow change didn’t behave as expected
You want to revisit an older onboarding setup
You need to check what changed (and when)
Multiple team members are editing journeys
You want peace of mind before making big updates
Good to Know
A new version is saved every time you publish
Restoring a version does not automatically publish it, you can review it first
You can always see which version is currently in use
Version names can be edited for clarity


