# Page Not Found

The URL `f.a.q./wallet/11.-why-was-my-withdrawal-canceled` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [11. Why was my withdrawal cancelled?](https://faq.rollercoin.com/rollercoin/f.a.q./wallet/11.-why-was-my-withdrawal-cancelled.md)
- [13. Why didn't my withdrawal arrive?](https://faq.rollercoin.com/rollercoin/f.a.q./wallet/13.-why-didnt-my-withdrawal-arrive.md)
- [12. How to cancel my withdrawal?](https://faq.rollercoin.com/rollercoin/f.a.q./wallet/12.-how-to-cancel-my-withdrawal.md)
- [14. Why can't I make a withdrawal?](https://faq.rollercoin.com/rollercoin/f.a.q./wallet/14.-why-cant-i-make-a-withdrawal.md)
- [8. How to make a withdrawal?](https://faq.rollercoin.com/rollercoin/f.a.q./wallet/8.-how-to-make-a-withdrawal.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://faq.rollercoin.com/rollercoin/f.a.q./wallet/11.-why-was-my-withdrawal-cancelled.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://faq.rollercoin.com/rollercoin/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://faq.rollercoin.com/rollercoin/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/rollercoin/f.a.q./wallet/11.-why-was-my-withdrawal-cancelled.md`).

You may also use `Accept: text/markdown` header for content negotiation.