> For the complete documentation index, see [llms.txt](https://support.emarketeer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-wait.md).

# Wait

Journey step that pauses the contact for a set amount of time before the next step.

The Wait step pauses the contact for a set amount of time. When the time has passed, the contact moves on to the next step.

<div align="left" data-with-frame="true"><img src="https://2894606528-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0ywqCs3au1x0DqPhEJTR%2Fuploads%2Fgit-blob-b359c052a287dd745e80a423a811f315dd33537e%2Fjourney-step-wait-settings.png?alt=media" alt="Wait dialog with Delay for set to 3 days"></div>

## Settings

* **Delay for** — enter a number and choose a unit, such as days.

Click **Apply** to save the step.

A Wait step is often placed before an [If / Else](https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-if-else.md) step, to give the contact time to act before the condition is checked.

{% hint style="info" %}
Always add a wait step before an If / Else step, or it will be evaluated immediately. This is especially important when you evaluate interactions from a previous step, such as an email open.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.emarketeer.com/guides/journeys/journey-steps/journey-step-wait.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
