What should be done to edit a condition after a journey has been published?

To edit a condition after a journey has been published, the correct course of action is to open the live journey, create a new version, make the necessary edits, and then publish the changes. This process ensures that any adjustments are made systematically and that the integrity of the original journey is preserved until the new version is thoroughly reviewed and finalized.

This approach allows for version control, meaning that the original configuration of the journey is maintained in case any issues arise or if the need arises to revert back to it. Creating a new version also provides a clear record of changes made, contributing to better tracking and analysis of performance over time.

Directly editing a published journey without restrictions is not advisable as it can lead to unintended consequences, disrupt the flow of the journey, or affect the user experience adversely. Deleting the current journey and creating a new one can be inefficient and may lead to the loss of valuable data or insights that the original journey contained. Simply notifying the team for approval before making edits does not actively address the need for version management and risk mitigation in the journey editing process.