> For the complete documentation index, see [llms.txt](https://support.growlytics.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.growlytics.in/journeys-and-automation/journeys-basics/journey-statuses.md).

# Journey Statuses

A Journey can be in one of four statuses: Draft, Running, Suspended, or Stopped.

<figure><img src="/files/p6an9twuJd2UCCAoKiNu" alt=""><figcaption><p>Journey Status</p></figcaption></figure>

### Draft Journey

On creation of the journey, it rests in the Draft status by default. This indicates that you are currently building and configuring the journey. Once you are done with journey building, you can switch from 'Draft' to 'Published' (or 'Running').

### Running Journey

Published journey also known as Running Journey, will accept customers into a journey, process them and send the required communication specified at each journey step.

Learn more about Running Journeys here: [Running Journey](/journeys-and-automation/journeys-basics/journey-statuses/running-journey.md)

### Suspended Journey

When a journey is no longer needed and you want to stop customers from entering a journey, you can suspend the journey. When the journey is suspended, no new customers will enter the journey however, existing customers in that journey will be processed.

Learn more about Suspended Journeys here: [Suspended Journey](/journeys-and-automation/journeys-basics/journey-statuses/suspended-journey.md)

### Stopped Journey

When a journey is no longer needed and you want to stop customers from entering a journey, you can pause the journey. When the journey is paused, no new customers will enter the journey however, existing customers in that journey will be processed.

Learn more about Stopped Journeys here: [Stop Journey](/journeys-and-automation/journeys-basics/journey-statuses/suspended-journey.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.growlytics.in/journeys-and-automation/journeys-basics/journey-statuses.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.