> For the complete documentation index, see [llms.txt](https://docs.runbot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runbot.io/triggers-boxes/adjust-position-rules/delay-between-two-triggers.md).

# Delay between two triggers

**Number of candles to wait before considering a new trigger signal so you can increase or decrease your position once more.**

*Ex: \[Increase order size by 10%] \[Delay between two triggers: 2] \[candles of timeframe 1h]*

*-> Current position is long 10 000$. An 'increase long signal' is triggered at 1:00 PM. Position is increased to 11 000$ at 1:00 PM.*

*-> Another 'increase long signal' is triggered, 10 minutes later, at 1:10 PM. The increase order is rejected, because the strategy must wait a minimum of 2 hours (2 x 1h) since the last increase order. Current position is still 11 000$.*

*-> Next 'increase long signal' is triggered at 4.00 PM. Since there was no 'increase long order' in the past 2 hours, the order is confirmed. Long position is now 12 100$ (11 000$ + 11 000$ \* 10%)*


---

# 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.runbot.io/triggers-boxes/adjust-position-rules/delay-between-two-triggers.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.