From e6d1d035edb14d44caa4316754860d01e7054f85 Mon Sep 17 00:00:00 2001 From: Liz Kane <68755692+lizkane222@users.noreply.github.com> Date: Wed, 21 Aug 2024 14:29:25 -0700 Subject: [PATCH 1/2] Update journeys-edits.md info on Journey Settings --- src/engage/journeys/journeys-edits.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/src/engage/journeys/journeys-edits.md b/src/engage/journeys/journeys-edits.md index 1f207ee9de..4fef3979ce 100644 --- a/src/engage/journeys/journeys-edits.md +++ b/src/engage/journeys/journeys-edits.md @@ -35,6 +35,10 @@ After you’ve published, users who meet the entry criteria can enter the new jo You can return to the Journeys list page to view the new live journey and its previous versions, which are nested under the journey container. +> info "Journey settings" +> A Journey's settings cannot be edited once the Journey has been published. This includes the [Entry settings and Exit settings](https://segment.com/docs/engage/journeys/build-journey/#journey-exits-and-re-entry). The only settings that can be edited after a Journey is published are the Journey's name and description. + + ## Working with Journeys versioning ### Exit settings and user flow between journeys @@ -61,4 +65,4 @@ Adding a list destination to a journey version creates a new record in Segment For example, if you add a list destination to Version 1 of a journey, and users begin flowing into the version, then Segment will begin creating the new record. If you create a Version 2 draft from Version 1 of the journey while Segment is still creating the new record, you won’t be able to publish Version 2 until this process is completed. -If the version has a list destination but no users have flowed into the version, though, Segment won't create a new record for that list destination and you won't have to wait to publish a new journey version. \ No newline at end of file +If the version has a list destination but no users have flowed into the version, though, Segment won't create a new record for that list destination and you won't have to wait to publish a new journey version. From fef1a7f2ad59b07baaa674f04fedbf27a38d62bb Mon Sep 17 00:00:00 2001 From: pwseg <86626706+pwseg@users.noreply.github.com> Date: Thu, 3 Oct 2024 11:55:41 -0500 Subject: [PATCH 2/2] minor rewording --- src/engage/journeys/journeys-edits.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/engage/journeys/journeys-edits.md b/src/engage/journeys/journeys-edits.md index 4fef3979ce..fccae5eb7e 100644 --- a/src/engage/journeys/journeys-edits.md +++ b/src/engage/journeys/journeys-edits.md @@ -36,7 +36,7 @@ After you’ve published, users who meet the entry criteria can enter the new jo You can return to the Journeys list page to view the new live journey and its previous versions, which are nested under the journey container. > info "Journey settings" -> A Journey's settings cannot be edited once the Journey has been published. This includes the [Entry settings and Exit settings](https://segment.com/docs/engage/journeys/build-journey/#journey-exits-and-re-entry). The only settings that can be edited after a Journey is published are the Journey's name and description. +> A Journey's settings can't be edited once the Journey has been published, including [entry and exit settings](/docs/engage/journeys/build-journey/#journey-exits-and-re-entry). The only settings you can change after publishing a Journey are the Journey's name and description. ## Working with Journeys versioning @@ -65,4 +65,4 @@ Adding a list destination to a journey version creates a new record in Segment For example, if you add a list destination to Version 1 of a journey, and users begin flowing into the version, then Segment will begin creating the new record. If you create a Version 2 draft from Version 1 of the journey while Segment is still creating the new record, you won’t be able to publish Version 2 until this process is completed. -If the version has a list destination but no users have flowed into the version, though, Segment won't create a new record for that list destination and you won't have to wait to publish a new journey version. +If the version has a list destination but no users have flowed into the version, though, Segment won't create a new record for that list destination, and you won't have to wait to publish a new journey version.