Understand how Journey changes affect versioning

Modified on: Tue, 8 Sep, 2026 at 7:41 PM

Admins can use the following table to understand how different Journey changes affect versioning. Structural changes, such as adding, removing, or reordering phases or activities, and changes to triggers or conditions create a new Journey version. Updates to Journey data, such as form data, do not create a new version. This guidance helps admins plan Journey updates and understand whether changes apply to existing requests or require a new version.

Activity versions are managed internally. Customers see only the Journey version.

Action	Change type	Version bump
Add or remove an activity	Structural change	Yes
Add or remove a phase	Structural change	Yes
Change the phase trigger	Structural change	Yes
Change phase-level conditions	Configuration change	Yes
Change the activity trigger	Configuration change	Yes
Change activity conditions	Configuration change	Yes
Mark an activity as mandatory	Configuration change	Yes
Mark an activity as non-mandatory	Configuration change	Yes
Change activity metadata, such as due date or planned start date	Data change	No
Edit activity or phase titles, descriptions, or labels	Data change	No
Add or remove Journey data from an activity	Data change	No
Edit the Journey plain task form from Admin settings	Status quo; only the latest form is maintained	No
Change the group to which the initiator belongs	Configuration change	Yes
Change the workspace for a Service Request activity	Configuration change	Yes
Change the agent group for a Service Request activity	Configuration change	Yes
Change the requester for a Service Request activity	Configuration change	Yes
Change the Requested for value for a Service Request activity	Configuration change	Yes
Change the due date for a Service Request activity	Data change	No
Add or remove a service item from a Service Request activity	Configuration change	Yes
Change the stakeholder for a form	Configuration change	Yes
Add a field to a form	Non-breaking change	No
Delete a field from a form	Configuration change; dependencies must be validated before deletion	Yes
Mark a form field as mandatory	Configuration change	Yes
Change form field conditions	Configuration change	Yes
Change a form field label	Data change	No
Add a choice to a dropdown field	Data change	No
Remove a choice from a dropdown field	Data change	Yes
Rename a choice in a dropdown field	Data change	No
Edit a Knowledge Base task	Data change	No
Edit an Email activity	Data change	No
Add or remove a child activity from a Service Request	Configuration change	Yes
Add, remove, or update stakeholders	Data change	No
Update the Admin setting to allow updates	Data change	No
Update the Admin setting to allow skipping	Data change	No
Change the Journey Request Assignment Group in Admin settings	Data change	No