20 Aug 2024: A version history for Journeys

Neelke Stadler Updated by Neelke Stadler

We all make mistakes. Having a way to revert to a previous working version of a chat journey is superb!

At times we introduce breaking changes when working on a chat journey, and although it was unintended you need to get back to a working version as soon as possible. Similarly when working as a team, it is helpful to know who made the last edit to a journey so that you know who to reach out to if you have questions or need to troubleshoot something. Having a version history of a journey makes both possible.

A version history for Journeys

Keeping track of work automatically makes life better. Let's look at what you can do with journey versioning. This apply to Canvas journeys only.

Notify the last editor on opening the canvas

If you edited a journey and, when returning to it, someone else edited it — you'd be notified.

Name a version

To help you keep track of versions of your service — you can "save" a specific version and give it a name to make it more prominent in the UI.

Restore a version

When you restore a version, that version is restored to the top of the version history, making it the most recent version and keeping the recent changes as older versions.

Filter between all versions and named versions

To make it easy to find a version of value, you can use the filter to find: All versions, Just named versions, Just auto-saves.

As always, we would love to hear your feedback.

Was this article helpful?

29 Aug 2024: Send reminders to Segments

15 Aug 2024: Faster and more reliable

Contact