> 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/support/troubleshooting.md).
# Troubleshooting
Fix skipped buys, paused copies, low balances, pending trades and alert-routing issues.
Find the message you're seeing and follow the corresponding checks.
## A copied buy was skipped
A skip means we did not place that buy. Open the notification for the reason: it might be below the minimum trade size, outside your first-buy preference, blocked by price impact or missing available SOL.
{% columns %}
{% column %}
**Minimum size:** check your trade-sizing settings.
{% endcolumn %}
{% column %}
**First-buy check:** review the chosen entry restrictions.
{% endcolumn %}
{% endcolumns %}
{% hint style="info" %}
The timing information shown in these example notices is specific to those events. It does not represent a guaranteed alert or execution time.
{% endhint %}
## A buy or sell hasn't completed
Check **Positions**, your wallet and any subsequent trade notification. A submitted transaction may still fail or settle later. Avoid repeatedly submitting the same operation until the outcome is clear.
## Your copy is paused
Open **Copies** and inspect its status. Confirm whether you paused new buys for one caller or selected **Pause everything**, which can also stop protective exits.
## Your balance looks lower than expected
Compare **Wallet total**, **Available**, **Reserved** and **Kept for exit fees**. Network fees, pending withdrawals and open orders may affect what you can spend.
## Alerts Routing cannot verify your channel
Check that you selected the correct group or channel, gave the bot the required permissions and followed the forwarding or chat-ID instructions. Then use the verification action again.
## Still need help?
Ask the community
For account-specific problems, include the error wording and approximate time. **Never include a private key, seed phrase or authentication code.**
---
# 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/support/troubleshooting.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.