# Pausing and Resuming a Journey

There might be conditions that you need to pause a live campaign. For example, if a snowstorm affects deliveries for a specific campaign, you can pause it and start it again when the weather is more favorable. Or, perhaps the journey isn't producing the results you expect. You can pause the journey and fix the issues.

Review how to identify a [journey's status quickly](/products/customer-data-platform/journey-orchestration/batch/understanding-journey-statuses).

This topic includes:

* [Pause a Journey](/products/customer-data-platform/journey-orchestration/batch/pausing-and-resuming-a-journey#pause-a-journey)
* [Resume a Journey](/products/customer-data-platform/journey-orchestration/batch/pausing-and-resuming-a-journey#resume-a-journey)
* [Edge Cases: Journey Pause/Resume Actions and Parent Segment Refreshes](/products/customer-data-platform/journey-orchestration/batch/pausing-and-resuming-a-journey#edge-cases-journey-pauseresume-actions-and-parent-segment-refreshes)


# Pause a Journey

Review the following list to understand what pausing a journey means to other objects within the journey:

* **Parent segment** : When the parent segment runs, the parent segment does not update the journey.
* **Profile activities** : Profiles do not progress to the next stage. Additionally, no profiles can be added to or removed from the journey.
* **Wait steps** : Wait steps do not increment while a journey is paused. If you pause a journey and a profile is on Day 1 of the wait step, it remains on Day 1 until the journey is resumed.
* **Activations** : No activations start while a journey is paused. You can edit the journey's name and activation settings. You cannot change the activation schedule.
* **Journey name and stages** : You can edit a journey name.


* Avoid pausing and resuming a journey multiple times on the same day. If there is a Parent segment refresh and you pause or resume a journey multiple times during the refresh, the data might be outdated for the day.
* Do not run an activation from Data Workbench while a journey is paused.


1. Open TD Console.
2. Open **Audience Studio**.
3. Navigate to a segment that contains the journey you want to pause.
4. Select **Versions**.


![](/assets/pausing-and-resuming-a-batch-journey-version-2024-05-10-1.f75cb0eec0c425fafe47dc0482987616ddef66aee2c0dd6b55b75930d1179492.9e7171ae.png)

1. Select a version with a version status of Live.
2. Choose one of the following:


* Select the green Live button.
* Select the ellipses at the end of the version row and then select **Pause**.


1. The journey transitions from Pausing to Paused.


# Resume a Journey

Review the following list to understand what happens when you resume a paused journey.

* **Parent segment** : When you resume the journey, when the parent segment updates, the journey resumes updating.
* **Resume journey on the same day** : Resume the journey before the parent segment's run time.
* **Resume journey to send activation on the same day** : Resume the journey before the activation runs.


1. Navigate to your paused journey and open it.
2. Select **Paused**.


The journey transitions from Launching to Live.

# Edge Cases: Journey Pause/Resume Actions and Parent Segment Refreshes

After you pause and resume a journey, you need to know how a parent segment refresh might affect a journey's progression. There might be certain scenarios where the journey will skip events.

## Scenario A Example

![](/assets/scenario1.c27d05de3157bd3db10c69fa33bd83c536ba119b9beacb060502b508fda620b7.9e7171ae.png)

* Day 1: Journey A is launched, and the Parent Segment refreshes. Journey A is paused. Activation 1 is skipped because Journey A is paused after the Parent Segment refreshes but before Activation 1 is scheduled to run.
* Day 2: Journey A resumes and the Parent Segment refreshes. Journey A completes Wait Step 1 and Activation 2 is launched.


## Scenario B Example

![](/assets/scenario2.bad426d3e3ec8ca0b0a298f79754a24073b03ca402a93152783707d702ffdbca.9e7171ae.png)

* Day 1: Journey A is launched, and the Parent Segment refreshes. Activation 1 is launched and Journey A is paused. Activation 2 is skipped because Journey A is paused.
* Day 2: Activation 2 is skipped because Journey A is still paused.
* Day 3: Journey A resumes and then the Parent Segment refreshes. Journey A completes Wait Step 1 and Activation 3 is launched.


See also [Journey FAQs](/products/customer-data-platform/journey-orchestration/batch/journey-faqs).