Journey editing

Both draft and active journeys can be edited. You may need to update journey elements in the following cases:

• Test the effectiveness of your communications
• Adjust a journey to some special events and changing conditions
• Edit occasional errors

Editing a draft journey

To edit an element of a journey that has not yet been launched, simply double-click on it. You can learn more about setting up each element in the journey elements article.

If you need to delete an element of a draft journey, select this element and click on the trash icon:

Editing an active journey

To edit an active journey, you first need to pause it. Click on the campaign’s dropdown menu and select Pause to edit.

While the journey is paused, no new users enter it. Users who already entered stay in the journey and continue from where they left off once you resume it. See What happens to users already in the journey when you pause it for details on specific elements.

Edit elements on the canvas

Modify and delete elements the same way as in a draft journey. Double-click an element to open its settings.

Note

If you change the content of a push, in-app, email, or SMS, all users receive the new version after you resume the journey.

Delete or add elements

If you delete an element, connect the remaining elements to each other or to a new element if you add one:

Leaving a branch without an outgoing connection is also a valid way to end it. On the canvas, an open branch end shows a small hint icon with a counter of how many users left there. In statistics, these departures count under Exits, not as an error.

Caution

After deleting an element, all statistics on it will be lost. If you need these statistics, we recommend saving them somewhere before editing a journey.

Save changes

Pushwoosh saves your changes automatically while you edit a draft or paused journey, so saving by hand isn’t required. The status below the campaign name tells you what to do:

• Not saved: autosave hasn’t saved your edits yet. No action needed. It saves automatically about 10 seconds after you start editing. Closing the tab or navigating away before then doesn’t lose the edit. It stays cached in this browser and picks up again when you reopen the journey here.
• Saved: your edits are saved. This appears briefly after each successful save, then the status goes back to showing the campaign name.
• Saved only in this browser: autosave couldn’t reach the server. The status turns orange in the header, and a banner appears below the canvas with a Save again button.

The banner below the canvas repeats this information with a way to retry:

A change marked Saved only in this browser stays in this browser’s local storage: it survives a reload here, but won’t reach other browsers or devices until a save succeeds. Click Save again to retry immediately. Otherwise, Pushwoosh keeps retrying in the background and clears the banner once a save goes through.

If you try to leave the page while the latest change hasn’t reached the server, Pushwoosh asks whether to Leave anyway or Stay:

Leaving without saving doesn’t discard the edit. It stays cached in this browser and picks up again when you reopen the journey here.

Resume the campaign

When you finish editing, click Resume campaign at the top right of the canvas.

For journeys with Audience-based entry, the resume step shows additional audience options. See Resume options for Audience-based entry.

What happens to users already in the journey when you pause it

Pausing a journey does not stop users who already entered it: they continue from where they left off once you resume it. What happens to a user in the meantime depends on which element they were waiting at when you paused.

A user is waiting at a Time Delay

Pausing the journey does not pause the Time Delay timer: the send time is fixed the moment the user enters the delay point, not when the journey resumes.

• If that time falls inside the pause window, the user is parked and the message goes out immediately once you resume the journey.
• If it falls after you resume, the message goes out at the originally scheduled time, as if the pause never happened.

For example, a user enters a 24-hour Time Delay on Monday at 10:00, so the message is scheduled for Tuesday at 10:00. Pause the journey Monday at 15:00 and resume it Wednesday: the message sends immediately on resume. Pause it Monday at 15:00 and resume Tuesday at 08:00 instead: the message still sends at the originally planned Tuesday 10:00.

Caution

A user waiting at a Time Delay is lost, not parked, if you pause the journey for longer than 7 days (parking expires silently, with no log or metric), if you select Stop campaign or Archive while paused, or if you delete the Time Delay element during editing. See Pausing a journey while a user is waiting for details.

A user is waiting at Wait for Trigger

A user who reached the Wait for Trigger element but has not yet triggered the specified event is lost if the event waiting period ends while the journey is paused.

A user is waiting on the Opened/Not opened split

A user who received a message just before you paused the journey, in a flow with Split flow if message is opened turned on, drops off if the wait time for that split ends before you resume the journey.

Resume options for Audience-based entry

After you pause the journey, edit it (e.g. change message content or add steps), and click Resume campaign, the Audience-based entry element shows options that depend on the current Entry schedule setting. These options control how users are treated when the journey resumes.

No scheduled entry date

If Entry schedule is One-time entry and Immediately (users entered at launch, no date was set), choose how the audience is handled when the journey resumes:

• Do not re-enter audience into campaign upon resuming (default)
  Users who previously entered will not re-enter the journey. They will continue from where they left off.

• Re-enter audience into campaign upon resuming
  Users who still match the segment criteria will be allowed to re-enter the journey upon resuming if the Campaign entry limit settings allow re-entry, and the user is not currently in the journey.

  This means users who previously entered and are no longer active in the journey can be re-added if both conditions are met.

Scheduled entry date

If Entry schedule is One-time entry and Schedule for a specific day, select what happens for users whose scheduled entry time (in their local timezone) has already passed:

• Exclude users whose local time has passed
  Users whose local scheduled time (e.g. 10:00) has already passed will not enter the campaign.
• Let users enter immediately
  Users whose local time has already passed will enter the campaign immediately when it resumes.

Important

If you previously set Schedule for a specific day to a date (e.g. August 5) and that date has already passed, selecting a new future date (e.g. August 8) triggers a different system behavior: the campaign will reprocess the audience. As a result, all users who match the audience segment at the time of the new launch will be added to the campaign, provided that the Campaign entry limit settings allow re-entry, and the user is not currently in the journey. This applies even if they had already entered on the original date.

In the After resuming the campaign section, choose how the audience is handled when you click Resume campaign:

• Do not re-enter audience into campaign upon resuming (default)
  Users who previously entered will not re-enter the journey. They will continue from where they left off.

• Re-enter audience into campaign upon resuming
  Users who still match the segment criteria will be allowed to re-enter the journey upon resuming if the Campaign entry limit settings allow re-entry, and the user is not currently in the journey.

View journey change history

You can track all changes made to the journey in the History panel, located on the right side of the journey builder. To open it, click the clock icon at the bottom-right corner of the canvas.

The panel displays a detailed log of when each update occurred, who made the change, and what was modified (e.g., campaign launch, entry conditions). This helps maintain transparency and version control throughout the journey’s lifecycle.

Each entry can be expanded to view specific changes made to individual journey elements.