> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/build/workflows/steps/wait.md).

# Wait Step

Pause workflow execution for a set amount of time.

The **Wait** step pauses a lead's progression through the workflow for a fixed duration before continuing to the next step.

The wait starts once the previous step finishes. For example, if an email is held by the mailbox's daily send limit, the wait starts when that email actually sends.

<figure><img src="https://4072969777-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FreCGkFdsmuPJzGP9ZgGA%2Fuploads%2Fgit-blob-2ca3d91ef33e086f3a8309e54c0cb496b2a6c98f%2FWorkflow%20Wait%20Step.png?alt=media" alt=""><figcaption><p>The Wait step configuration panel.</p></figcaption></figure>

## Configuration

Set the **duration** and **unit**:

* **Minutes**: e.g., 30 minutes
* **Hours**: e.g., 4 hours
* **Days**: e.g., 2 days

The minimum duration is 1 unit (1 minute, 1 hour, or 1 day). The maximum is **30 days**.

{% hint style="info" %}
For scheduling a send at a specific clock time rather than a relative delay, configure an outgoing window on the sending step instead — see [Send Email Step](https://docs.spara.com/build/workflows/steps/send-email.md).
{% endhint %}

## Common Patterns

{% columns %}
{% column %}
**Give leads time to act**

Place a Wait before a follow-up step. For example: send an email, wait 2 days, then call phone if no reply.
{% endcolumn %}

{% column %}
**Space out outreach**

Avoid contacting leads too frequently by adding Wait steps between Send Email, Send Text, and Call Phone steps.
{% endcolumn %}
{% endcolumns %}

## Behavior During Unpublish/Republish

If a workflow is unpublished while a lead is mid-wait, that lead's timer is paused. When the workflow is republished, the timer resumes from where it left off.


---

# 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://docs.spara.com/build/workflows/steps/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.
