> For the complete documentation index, see [llms.txt](https://docs.buoy.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buoy.finance/for-depositors/cancelling-a-request.md).

# Cancelling a Request

Requests on Buoy are normally settled within minutes. But if one is ever left hanging — for example during an outage of the settlement service — you can always take your funds back yourself. **No request can strand your assets.**

## The cancellation window

Every pending request card shows a live countdown: **"Cancellable in …"**. Once the timeout passes (currently **30 minutes** after your request), the countdown is replaced by a **Cancel deposit** / **Cancel withdrawal** button.

The waiting period exists to give the settlement service a fair chance to fulfill your request at the correct price before you can pull it back.

## What you get back

| Request    | State when cancelled | What returns to your wallet                                                                                          |
| ---------- | -------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Deposit    | Pending              | Your full USDC amount                                                                                                |
| Withdrawal | Pending              | Your Buoys, untouched                                                                                                |
| Withdrawal | Locked               | Your original Buoys, re-minted (the fixed USDC payout is released — you get back the same number of shares you held) |

{% hint style="warning" %}
The **request fee in HYPE is not refunded** on cancellation. It's a small fixed amount (currently 0.01 HYPE), charged when you submit the request.
{% endhint %}

One detail on cancelling a **Locked** withdrawal: if locking your payout crystallized a performance fee (because it happened at a new share-price high), those fee shares were minted to the Leader at that moment and **stay minted**. You get your own shares back in full — you just don't rewind a fee that was already earned by the vault's performance.

## When should you cancel?

* **Don't rush.** Under normal conditions requests settle long before the 30-minute mark. A request that's a few minutes old is not stuck.
* **Withdrawal taking longer than expected?** That's often the vault freeing up cash (bridging or closing positions), not a failure — your payout, once Locked, is recorded on-chain and safe. See [Withdrawing](/for-depositors/withdrawing.md).
* **Cancel when you actually want out** — if the request is past the timeout and you'd rather have your USDC or Buoys back now than wait for settlement, cancelling is always safe. You can simply submit a new request afterwards.

## One special case worth knowing

A withdrawal can occasionally sit unsettled because the vault's share price dropped below your quoted **minimum out** — the protocol refuses to pay you less than your guaranteed floor, so it waits for the price to recover. If it doesn't recover and you'd rather exit at the lower price, cancel the request (reclaiming your Buoys) and submit a fresh withdrawal, which will be quoted at the current share price.


---

# 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.buoy.finance/for-depositors/cancelling-a-request.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.