> 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/entry-in-position-rules/no-end-trade-check.md).
# No end trade check
### Overview
The **“No End Trade Check”** rule is an entry condition modifier that controls whether your strategy **immediately re-evaluates trade entry conditions after a position closes**.
By default, Runbot does **not** check entry triggers instantly at the end of a trade. Instead, entry is re-checked:
* On the **next indicator update** that modifies a signal, or
* On the **next trade-triggering event** (like a new candle or market condition)
This setting gives you **explicit control** over that behavior.
### What This Condition Does
When **enabled**, it tells Runbot:
> ❌ **Do not** check the entry conditions right after closing a trade.\
> ✅ Wait for the next relevant update or signal change.
This prevents **immediate re-entry** into a trade based on old or unchanged signals.
### Why Use It?
This is especially useful for:
* **Pari-mutuel strategies** that reset after each round
* Avoiding accidental back-to-back trades due to unchanged signal states
* Maintaining consistency with strategy logic
***
### Default Behavior
* This rule is **enabled by default** on **older strategies** (to preserve current behavior)
* It is **not added automatically** on **new strategies**, but can be toggled manually in the strategy editor.
***
### Related Rule: No Previous Trade
If you want to delay re-entry for a specific number of candles after a trade, consider using the **"No Previous Trade (N candles)"** condition instead.
---
# 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/entry-in-position-rules/no-end-trade-check.md?ask=&goal=
```
`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.