> For the complete documentation index, see [llms.txt](https://help.refractbot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.refractbot.com/general-setup/task-creation/delays.md).

# Delays

* When creating tasks, there are two different delays to add: monitor delay and task delay

## Monitor Delay

* The monitor delay determines how often the monitor checks for product availability. Lower values mean the monitor will theoretically pick up products faster, but setting it too low can increase the risk of bans.

![](https://2861066425-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjdmk3RduT9OdU2B3zFmG%2Fuploads%2Fgit-blob-3249da265b1b9fa36f18da1b5eb86569f46a6d80%2Fdelays-monitor-delay.png?alt=media)

## Retry Delay

* Retry delay (sometimes called task delay) is the delay a task waits before retrying after an error. Errors include anything that prevents a clean, one-shot checkout, for example:

  * Out of Stock (OOS)
  * Rate limit
  * Shape block
  * Unknown response

  In other words, task delay does nothing during a perfect checkout flow (since there are no errors to delay). But when something fails, as is often the case, the task uses the task delay value before retrying again. It also has no effect on queue entry speed on queue sites.

![](https://2861066425-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjdmk3RduT9OdU2B3zFmG%2Fuploads%2Fgit-blob-1efb128a01b82b9a850f380f29ed11834f9e66ef%2Fdelays-retry-delay.png?alt=media)

{% hint style="info" %}
Both delays are required. Be careful as too low delays will result in proxy/IP bans
{% endhint %}

{% hint style="info" %}
**Changing a delay never stops or restarts your tasks.** Delay changes apply on the fly. Whether you should change them is a different question: stick with each site's defaults unless its guide says otherwise.
{% endhint %}

## Choosing the Right Delay

#### **Default Values**

* By default, Refract sets a recommended delay for each site. If you aren't sure what to use, stick with the default as it reflects the tested balance of speed and safety.

| Site     | Monitor Delay default | Retry Delay default | Notes                                  |
| -------- | --------------------- | ------------------- | -------------------------------------- |
| Walmart  | `4500`                | `4500`              | Default is fine                        |
| Target   | `3500`                | `3500`              | Users experiment between 1000 and 4000 |
| Amazon   | `3500`                | `3500`              |                                        |
| Best Buy | `3500`                | `3500`              |                                        |
| Apple    | `3500`                | `3500`              |                                        |

**Site-Specific Differences**

* Different sites perform best with different delays. Some sites tolerate very low delays, while others ban aggressively if you go too low. Always adjust based on the site you're running, and see the site's module guide for the details.


---

# 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://help.refractbot.com/general-setup/task-creation/delays.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.