> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/reference/step-definitions/wait-for-url.md).

# Wait for URL

{% hint style="info" %}
Applies to: DeployR 1.4 and later.
{% endhint %}

The **Wait for URL** step pauses the task sequence until the specified URL responds with HTTP status 200 (OK). Use it when the next steps depend on a web service or other resource that might not be ready yet, for example a service that another process brings online.

| Option          | Description                                                   |
| --------------- | ------------------------------------------------------------- |
| URL to wait for | The URL that must respond before the task sequence continues. |

The step requests the URL every 15 seconds, with a 5-second timeout for each request, and logs a message each time it is not available yet.

{% hint style="warning" %}
There is no overall time limit. If the URL never becomes available, the task sequence waits indefinitely, so check the URL carefully.
{% 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://documentation.2pintsoftware.com/deployr/reference/step-definitions/wait-for-url.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.