> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/platform/risk/circuit-breakers.md).
# Circuit breakers and caps
Hard caps and circuit breakers stop an oversized order or a bad day before it becomes a breach.
Caps stop a single order from being too big. Circuit breakers stop an account from trading after a bad day. Both apply before Breach Guard, and both apply to every order, manual or automated.
## Caps on every order
| Name | What it means |
| -------------------------- | ------------------------------------------------------ |
| **Per-order notional cap** | The largest single order the account can send. |
| **Daily notional cap** | The most the account can trade in total in one day. |
| **Max open positions** | How many positions can be open at once. |
| **Max leverage** | The highest leverage an order can use. |
| **Risk dial** | The ceiling on risk per trade. Nothing sizes above it. |
## Checks before an order is sent
Every order is checked against the instrument's rules: tick size, step size and minimum and maximum quantity. The margin it needs must be no more than 95% of the account's equity. Market orders are checked against the top of the book before sending. Fills can still slip. If any check fails, the order is rejected with a reason and the rejection is logged.
## Circuit breakers
{% hint style="info" %}
**Coming soon.** Circuit breakers are not live yet. This section describes how they will work.
{% endhint %}
| Name | What it means |
| -------------------------------- | -------------------------------------------------------------------------- |
| **Per-account daily -R breaker** | After the account loses a set number of R in a day, new entries will stop. |
| **Global breaker** | Will stop new entries on every account at once. |
A breaker will stop new entries only. You will always be able to close a trade.
{% hint style="warning" %}
A rejected order does not mean something is broken. Read the reason first. It is usually a cap doing its job.
{% endhint %}
## Next steps
---
# 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://docs.tradesurge.co/platform/risk/circuit-breakers.md?ask=&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.