> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/studio/nodes/action-nodes/delay.md).

# Delay

Pause a workflow for a set amount of time or until a specific date and time.

## Delay

### What does it do?

The **Delay** node holds the next step for a chosen amount of time. Think of it like telling an assistant, "Do this task later, not now."

Use it when timing matters, such as sending a follow-up later or spacing out repeated actions.

#### Smart features

* **Supports two timing modes**: choose **Delay for** to wait a set amount of time, or **Delay until** to resume at an exact date and time.
* **Converts time for you**: if you enter minutes, hours, or days, Diaflow turns that into one clear wait value automatically.
* **Calculates the remaining wait automatically**: when you choose **Delay until**, Diaflow works out how long it is from now until that date and time.
* **Keeps the output simple**: the node returns one delay value that Diaflow uses to decide when the next step should run.

<figure><img src="https://3864624312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRdo1pkMnofwxf3lpWftw%2Fuploads%2FCqgOOhyh5vmLourMEgF8%2FCap%202026-06-05%20at%2010.26.10.gif?alt=media&amp;token=ac45c7dd-0a07-4ced-be9a-6a3f6310ac9e" alt=""><figcaption></figcaption></figure>

### Real-World Business Value

* Wait 2 hours before sending a second outreach email, so contacts do not receive messages too quickly.
* Pause a workflow until the next morning before creating a reminder task for a sales rep.
* Space out status checks between systems to reduce repeated requests and avoid unnecessary failures.

### Step-by-Step Setup

* Drag **Delay** onto the canvas where you want the pause to happen.
* In **Type**, choose **Delay for** if you want to wait a fixed amount of time.
* If you choose **Delay for**, in **Delayed for**, select **Seconds**, **Minutes**, **Hours**, or **Days**.
* If you choose **Delay for**, in **Value**, enter the number of seconds, minutes, hours, or days to wait.
* In **Type**, choose **Delay until** if you want the workflow to continue at an exact date and time.
* If you choose **Delay until**, in **Value**, select the date and time you want.
* Save the node and run the workflow once to confirm the next step resumes when expected.

### The Transformation: Before & After

**Before  settings entered in the Delay node**

<figure><img src="https://3864624312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRdo1pkMnofwxf3lpWftw%2Fuploads%2FhzsDQXmFzIunoTwQSbEP%2Frounded-image%20-%202026-06-04T143956.416.png?alt=media&amp;token=5f134ca1-416a-494f-8778-eaebfcc52441" alt=""><figcaption></figcaption></figure>

**After  delay value prepared for the next step**

<figure><img src="https://3864624312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRdo1pkMnofwxf3lpWftw%2Fuploads%2FayIpeR5RN5mCUy7xdcps%2Frounded-image%20-%202026-06-04T143919.952.png?alt=media&amp;token=885b9d1d-03d2-4289-ac21-c61fb873a44b" alt=""><figcaption></figcaption></figure>

### Tips & Warnings for First-Timers

#### Best practices

* Use **Delay for** when you want a simple fixed pause.
* Use **Delay until** when the workflow must resume at a specific calendar time.
* For date-based scheduling, choose the date and time from the picker instead of typing custom formats by hand.
* Test one run first if the timing is important for a customer message, reminder, or deadline.
* For long waits tied to a real date, prefer **Delay until** over estimating with a large number of days.

#### Warnings

* Do not leave **Type**, time unit, or **Value** empty. The workflow can fail.
* Do not use unsupported time units. Use only **Seconds**, **Minutes**, **Hours**, or **Days**.
* Do not choose a date or time in the past. The workflow may continue immediately or behave unexpectedly.
* Do not paste unusual date text into **Delay until**. Use the standard picker format whenever possible.
* Do not assume timezone-sensitive schedules will always match your local clock without testing once first.
* Do not rely on this node to change your business data. It only controls when the next step runs.

### Need help?

* Learn the basics in [How a node works](/studio/lets-start-with-the-basics/how-a-node-works.md)
* Build the full flow in [Create a workflow](/studio/manage-a-workflow/create-a-workflow.md)
* Browse related nodes in [Component List](/studio/component-list.md)
