> 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.

![](/files/PmsvidOqgHCkyyXx5hI6)

## 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.

![](/files/vczWuLvUnj3vAYYYF2n8)

{% hint style="info" %}
Both delays are required. Be careful as too low delays will result in proxy/IP bans
{% 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-Specific Differences**

* Different sites perform best with different delays. For example, some sites can tolerate very low delays, while others will ban aggressively if you go too low. Always adjust based on the site you’re running. For more detailed specifications, please see each site specific guide. 


---

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