Overview

In the journey manager, the "status" column indicates the current state of a journey. Journey statuses help provide users easily identify the current state of a journey.

Statuses of a Manual Journey

Manual journeys can have one of the below-stated four statuses at any given point of time-

• Draft

  What it means: This is the initial version of the journey, similar to the first draft of an article. You can make edits or adjustments during this stage. If no changes are made, this draft becomes the final version of the journey, ready for review or further editing.

  Status Movement: The journey remains in the Draft state until you decide to proceed. Once you're ready, you can move the journey to the next stage by clicking "Run Journey" option.

• Running

  What it means: Once you click "Run Journey," the journey begins to execute. In this stage, the steps set up in the journey (such as sending messages to selected users) are carried out one by one on the audience (e.g., users in a profile list) in a random order. The status "Running" indicates that the journey is in progress.

  Status Movement: The journey remains Running state until it is either completed or manually stopped.

• Stopped

  What it means: You can manually stop a journey in the Running state. When stopped, the journey will complete execution for profiles already picked up but will not process profiles that haven’t yet started execution. This ensures that no further actions are taken for the remaining profiles in the audience.

  Status Movement: The journey can move from Running to Stopped when you choose to stop it. It remains in this state you choose to re-run the journey.

• Completed

  What it means: The journey status changes to "Completed" as soon as all profiles or leads in the segment/list have been picked for execution. However, this does not necessarily mean that the journey has been fully executed on every profile. There may be delayed nodes or scheduled actions within the journey that extend the execution timeline, making the journey for an individual profile a multi-day process or even more.

  Status Movement: The journey moves from Running or Stopped to Completed once all profiles have been picked up for execution.

Statuses of a Trigger-Based Journey

Trigger-based journeys can have one of the below-stated three statuses at any given point of time-

• Draft

  What it means: This is the initial state of the journey, similar to the draft status in manual journeys. During this stage, changes can be made, and versions can be upgraded. Stakeholders can review or collaborate on the journey, but it hasn't been finalized for execution yet.

  Status Movement: The journey remains in the Draft state until you are satisfied with it. Once ready, you can deploy it to the next stage (Active).

• Active

  What it means: After clicking "Deploy Journey," the journey enters the Active state. At this point, the journey is ready for execution. External systems or clients can now trigger the journey and start sending messages as part of the journey's steps. This is when the journey is live and actively working.

  Status Movement: You can stop the journey at any time, deactivating it and transitioning it from Active to Inactive.

• Inactive

  What it means: If the journey is deactivated (e.g., by clicking "Stop Journey"), it enters the Inactive state. In this state, the journey is not executing, and external systems can't trigger it. If someone tries to trigger an Inactive or Draft journey, they will be prompted to activate or deploy it before they can proceed

  Status Movement: A journey can move from Active to Inactive and vice versa. However, once in the Draft mode, the journey cannot go back to Draft from Active or Inactive; it can only move forward again once deployed to the Active state.

  Note: For Active journeys, users can make changes directly on the journey canvas and redeploy the journey without moving it back to Draft. This ensures zero downtime for automated journeys, allowing clients to continue triggering journeys and making requests 24/7 without any disruption.