> For the complete documentation index, see [llms.txt](https://docs.nected.ai/nected-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nected.ai/nected-docs/workflow/add-node/control-nodes/delay-node-renamed-wait-and-resume-node.md).

# Delay Node (Renamed Wait & Resume Node)

{% hint style="success" %}
The **Delay Node** has been **renamed and upgraded** to the **Wait & Resume Node**.\
While existing workflows using Delay will continue to function, all new workflows should use [**Wait & Resume**](/nected-docs/workflow/add-node/control-nodes/wait-and-resume-node.md).
{% endhint %}

The Delay node is a crucial tool in workflow design, allowing for the introduction of pauses for specified durations. This feature is particularly valuable for timing-based operations and rate-limiting API calls.

### Functionality

* **Pausing Workflows:** The primary function of the Delay node is to pause the execution of the workflow for a specified duration.
* **Timing-Based Operations:** It enables workflows to wait for a specific period before proceeding, which is useful for tasks that require timing precision.
* **Rate-Limiting API Calls:** Delay nodes can be employed to control the rate at which API calls are made, preventing excessive requests within a short timeframe.

### Conclusion

The Delay node provides a simple yet powerful mechanism for introducing pauses in workflows, enabling precise timing control and effective rate-limiting of API calls. By leveraging Delay nodes effectively, users can enhance the efficiency and reliability of their workflows.


---

# 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://docs.nected.ai/nected-docs/workflow/add-node/control-nodes/delay-node-renamed-wait-and-resume-node.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.