> For the complete documentation index, see [llms.txt](https://docs.pingu.exchange/pingu-exchange-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pingu.exchange/pingu-exchange-docs/trade/orders/cancellation-reasons.md).

# Cancellation Reasons

Orders can be cancelled for a range of reasons. These are indicated in your [History](/pingu-exchange-docs/trade/history.md) panel.

* **User-activated**: the order was cancelled by the user.
* **!Protected**: a protected market order was cancelled because it could not execute at the manually provided price or better.
* **!Reduce**: a reduce-only order was cancelled because there was no available position to reduce.
* **!Max-oi**: the order was cancelled because the [maximum OI](https://docs.pingu.exchange/pingu-exchange-docs/security/risk-mitigation#maximum-open-interest) on the market was reached.
* **!Max-delta**: the order was cancelled because the [m](https://docs.pingu.exchange/pingu-exchange-docs/security/risk-mitigation#maximum-open-interest)aximum delta on the market was reached.
* **!Max-size**: the order was cancelled because the submitted size exceeds the maximum size for this market.
* **!No-execution**: a limit or stop order was cancelled because it did not meet the price requirements relative to the current market price.
* **!Market-reduce-only**: this market is in reduce-only mode.
* **!Expired**: the order was cancelled because it [expired](https://docs.pingu.exchange/pingu-exchange-docs/trade/orders/order-types#expiry).
* **!Oco**: the order was cancelled by another order being executed or cancelled ([OCO](https://docs.pingu.exchange/pingu-exchange-docs/trade/orders/order-types#one-cancels-the-other-oco)).
* **!Pool-risk**: the order was cancelled due to the max pool drawdown being reached.


---

# 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.pingu.exchange/pingu-exchange-docs/trade/orders/cancellation-reasons.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.