> For the complete documentation index, see [llms.txt](https://callgraph.gitbook.io/callgraph-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://callgraph.gitbook.io/callgraph-docs/copy-trading/guards-and-exits.md).

# Guards and exits

Control price impact, slippage, limits, trade frequency and pause behavior.

Your trading guards help decide which caller trades are eligible for copying. Open **Copytrade → Settings** to review the controls.

<figure><img src="https://1024313129-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F19fy6z4ax7jX5gvABuYZ%2Fuploads%2Fgit-blob-6ab0b765ec547795370230906234d843f11bb1d9%2Fshot-04.png?alt=media" alt="Actual Copy Settings screen with account-wide guards, Fast mode and pause controls"><figcaption><p>Open each setting to review its value. Limits shown here reflect one account's choices.</p></figcaption></figure>

## Common guards

| Setting                              | What it controls                                     |
| ------------------------------------ | ---------------------------------------------------- |
| **Min caller buy size**              | Skip caller buys below your threshold                |
| **Max price rise after their buy**   | Avoid chasing a move too far from the caller's entry |
| **Max price impact**                 | Limit how much your trade could move the price       |
| **Slippage**                         | Control acceptable execution-price movement          |
| **Wait between buys**                | Set a cooldown between eligible trades               |
| **Max positions / Daily budget**     | Limit open exposure or daily spending                |
| **Buy each token once / Same token** | Control repeated entries                             |
| **Low-balance alert**                | Receive a warning when funds run low                 |

## Choose the right pause

{% tabs %}
{% tab title="Pause new buys" %}
Stop additional entries while keeping any separately configured eligible exits available.
{% endtab %}

{% tab title="Pause everything" %}
Stop new buys **and** automatic exit activity. Your open positions may be unprotected until you resume or manage them manually.
{% endtab %}
{% endtabs %}

{% hint style="danger" %}
**Pause everything can disable protective take-profit/stop-loss actions.** Check your open [Positions](/callgraph-docs/trading/positions-and-sells.md) before confirming it.
{% endhint %}

<details>

<summary>Why was my trade skipped?</summary>

A trade may fail a guard because the caller buy was too small, the price moved, estimated price impact exceeded your limit, your budget was exhausted or a token could not be checked. Open the skip notification for the specific reason, then use [Troubleshooting](/callgraph-docs/support/troubleshooting.md).

</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://callgraph.gitbook.io/callgraph-docs/copy-trading/guards-and-exits.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.
