> For the complete documentation index, see [llms.txt](https://docs.raidrobotics.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.raidrobotics.org/raidparts/manufacturing-guide/holds-and-cancels.md).

# Holds and cancels

## On hold means stop

An MO on hold shows a badge and a banner:

* **On hold · Cancel requested**: someone asked to cancel this MO.
* **On hold · Obsolete requested**: the design part may be retired.

Don't work it. RAIDParts won't let anyone start it, mark it done, fail it at QA or print its labels until an admin decides. The admin either approves (the MO is canceled and kept for records) or releases the hold (work picks up where it left off).

## Canceled means done

A canceled MO reads **Canceled** everywhere, with who canceled it and why. It never shows On hold. A part whose design was made obsolete shows a dark **Obsolete** badge with its name struck through, and its MOs read **Canceled**.

**Manufacturing › Parts** hides obsolete parts by default. Pick **Obsolete** or **All parts** in the status filter (or click **Show** next to the parts count) to see them. **On hold** lists only parts waiting on an admin.

## Ask to cancel an MO

1. Open the part from **Manufacturing › Parts** and select the MO.
2. Click **Request cancel**.
3. Say why. A reason is required.

The MO goes on hold, and the request appears in **Admin › Holds**. Admins see **Cancel MO** instead, which cancels it right away.

![Holds and cancel requests](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-09beaf3692fd74714ee35858086690f15d369e23%2F08-holds.png?alt=media)


---

# 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://docs.raidrobotics.org/raidparts/manufacturing-guide/holds-and-cancels.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.