Skip to main content
Every time you publish a journey, Courier saves a versioned snapshot. Version history lets you see what changed between publishes, compare any two versions side-by-side, and revert to a previous version if needed.

Opening Version History

In the journey editor, click the history button (the clock-with-arrow icon next to the Publish button) to open the version history page. The button is disabled if the journey has never been published. This opens the version history panel on the right side with a list of all previously published versions, each labeled with a version number (v1, v2, …) and a relative timestamp. The most recent version is marked Current.

Comparing Versions

Click any version in the list to see a side-by-side comparison: the selected version on the left and the current draft on the right. Both canvases are read-only. A banner at the top confirms which version you’re comparing (e.g., “Comparing Version v2 with Current Draft - Read Only”).
You can click individual nodes in either canvas to inspect how they were configured in that version. This lets you see the exact conditions, delay durations, template content, or schema fields that were active at a specific point in time. This is useful for understanding what changed when a journey’s behavior shifts unexpectedly.

Reverting to a Previous Version

Hover over any previous version in the list to reveal the Revert button. Click it, or click Revert to this version in the comparison banner at the top. This loads that version’s configuration into the editor as a new draft. You still need to publish the restored version for it to take effect. Reverting does not delete any versions. It creates a new draft based on the selected version; publishing it creates a new version entry in the history. The full audit trail is preserved.
Runs that started on a previous version continue executing against that version’s configuration. Reverting and re-publishing only affects new invocations.

What’s Next