> For the complete documentation index, see [llms.txt](https://docs.bitsafe.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitsafe.finance/cbtc/concepts-and-reference/errors-retries-and-troubleshooting.md).

# Errors, retries, and troubleshooting

### First rule

After a timeout or transport error, do not assume the command failed. Query the authoritative Canton, account, transfer-offer, or Bitcoin state before retrying.

### Error classes

| Class              | Examples                                      | Response                                       |
| ------------------ | --------------------------------------------- | ---------------------------------------------- |
| Configuration      | Wrong endpoint, party, package, network       | Stop and correct configuration                 |
| Authentication     | Expired token, wrong audience, missing rights | Refresh or correct access, then re-query state |
| Validation         | Bad amount, destination, offer, or contract   | Do not retry unchanged                         |
| Conflict           | Archived contract or concurrent action        | Refresh active state and rebuild               |
| Transport          | Timeout, disconnect, unavailable service      | Determine commitment before retrying           |
| External lifecycle | Bitcoin confirmation or attestation delay     | Monitor the existing workflow                  |

### Idempotency pattern

Use one business reference and command identifier for one intent where supported. Persist it before submission. On uncertainty, search by that reference and resulting contract or update identifiers.

### Retry policy

Retry only operations documented as safe. Use bounded exponential backoff with jitter for read-only transport failures. Do not automatically retry mint, redemption, transfer acceptance, cancellation, or account creation without checking state.

### Support evidence

Collect the environment, UTC time, release set, party, sanitized request reference, Canton update or contract identifiers, Bitcoin transaction identifier where relevant, error code, and logs with secrets removed.

### Related pages

* [CBTC authentication](/cbtc/get-started/authentication.md)
* [Mint CBTC](/cbtc/guides/mint-cbtc.md)
* [Redeem CBTC](/cbtc/guides/redeem-cbtc.md)
* [Transfer and receive CBTC](/cbtc/guides/transfer-and-receive-cbtc.md)
* [CBTC batch transfers and UTXO management](/cbtc/guides/batch-transfers-and-utxo-management.md)
* [Support and developer resources](https://docs.bitsafe.finance/support-and-developer-resources/)

### Next step

👉 **Still blocked?** [Support and developer resources](https://docs.bitsafe.finance/support-and-developer-resources/).


---

# 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.bitsafe.finance/cbtc/concepts-and-reference/errors-retries-and-troubleshooting.md?ask=<question>&goal=<endgoal>
```

`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.