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

# Troubleshooting

| Problem                                      | What to do                                                                                                                                                                     |
| -------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Wrong network or insufficient balance        | Use the token's network and leave enough gas for the request and claim.                                                                                                        |
| Approval succeeded but no request appears    | Approval and buying are separate wallet transactions. The app continues automatically only while fees and intent stay unchanged; check the current action and wallet activity. |
| Transaction is pending or timed out          | Check its hash and receipt before sending another.                                                                                                                             |
| Transaction reverted                         | Read the error and refresh balances, fees, and request state before retrying.                                                                                                  |
| Buy request cannot be cancelled              | Execution may have started. Only accepted buy requests can be cancelled.                                                                                                       |
| Sell request is preparing                    | Takes is releasing funds from positions. The request cannot be cancelled.                                                                                                      |
| Request processing is delayed                | Keep the request ID and transaction hashes. Transfers or account operations may still be pending.                                                                              |
| Claim succeeded but balance is unchanged     | Allow the page to catch up with the chain.                                                                                                                                     |
| Chart or PnL looks incomplete                | Check data age and transaction history. Missing data is not zero value.                                                                                                        |
| Basket did not publish                       | Keep the form open, correct field errors or sign in, and retry Publish basket. Leaving discards unpublished edits.                                                             |
| Deployment succeeded but confirmation failed | Choose Retry connection with the existing creation transaction. Do not deploy again.                                                                                           |
| Activation needs attention                   | Keep the creation hash and visible error for investigation.                                                                                                                    |

When reporting a problem, include the network, token address, transaction hash, and error. Never share a private key or recovery phrase.

See [Request status](/takes-docs/reference/status-reference.md#request-status) and [Support](/takes-docs/reference/support-and-official-links.md#support-and-security-contact).

For other product features, see [Trade](/takes-docs/trade.md), [Referrals](/takes-docs/referrals.md), and [Analytics](/takes-docs/analytics.md).


---

# 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://takes.gitbook.io/takes-docs/reference/troubleshooting.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.