What happens when users pause a journey?
Target Audiences node
| Filter by criteria | Trigger | |
| When Journey pauses | Stop searching for profiles that meet the criteria. Profiles already in node will not move to the next node. | All profiles with interactions during this period will not enter the Journey. |
| When Journey reactivates | Continue searching for profiles that meet the criteria. Profiles currently in node will move to the next node. | Only retrieve the profiles: – Before pausing the Journey – After resuming the Journey |
Channels and Message node
Including channels such as: Email, SMS, ZNS…
When pausing the Journey:
- Message building will be halted. Messages that are not yet finished will be resumed when the journey continues running.
- Messages that have been built will still be sent to profiles.
Wait node
1. Wait for a period of time or Wait until a specific time frame
- When the Journey is paused: The system still calculates the waiting time for the profile. In the case that the waiting time expires but the Journey has not reactivated, the profile will not move to the next node.
- When the Journey is reactivated: Profiles that have met the waiting time (during the period when the Journey was paused) will move to the next node. Profiles that haven’t met the waiting time will continue with the actions of the current block.
2. Wait until an Event occurs:
When the Journey is paused: The system continues to monitor whether profiles have triggered an event. If an event occurs, the profile remains held in the Wait block.
When the Journey continues: Profiles that have triggered an event are moved to the next block. Profiles that haven’t triggered an event remain in the Wait block.
3. Wait block within the Conditional Check – Event Triggered
When the Journey is paused: The system continues to monitor whether profiles have triggered an event. If an event occurs, the profile remains held in the Conditional Check node.
When the Journey continues:
- Profiles that trigger an Event → Follow the “Event Occurred” branch.
- Profiles that do not meet the event condition within the waiting period → Follow the “Event Not Occurred” branch.
- Profiles that haven’t met the event condition (waiting time is still remaining when the Journey continues) → Remain in the Conditional Check node.
Other nodes
- When the Journey is paused: Profiles is still within node, they just don’t exit the node.
- When the Journey continues: Proceed with the tasks associated with the block.