> 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/admin-guide/holds.md).

# Holds

Work that needs an admin decision goes on hold and stops on the shop floor until you decide in **Admin › Holds**.

![Admin › Holds with Order holds and Part holds, both empty](https://2105095865-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX3JOc9Z4ZYAoJCFFCn5v%2Fuploads%2Fgit-blob-cbc1c2aa90a467277a44bed157d3cde1941313bf%2Fadmin-holds.jpg?alt=media)

![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)

## Where holds come from

| From          | Action                                                                                            | Shows as                                                       |
| ------------- | ------------------------------------------------------------------------------------------------- | -------------------------------------------------------------- |
| Manufacturing | A manufacturer clicks **Request cancel** on an MO                                                 | Order hold, **Cancel requested**                               |
| Design        | A designer clicks **Make obsolete**, then **Send request**, on a part that's already been created | Part hold, **Obsolete requested**. Its open MOs go on hold too |

## Decide

| Queue       | Choices                                                                                                                                                                                          |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Order holds | **Approve cancel**: the MO is canceled and kept in MO History. **Release hold**: work resumes.                                                                                                   |
| Part holds  | **Approve obsolete**: open MOs are canceled and the design part becomes obsolete. **Release hold**: the part and its MOs can be worked again. (**Approve delete** appears for a delete request.) |

An MO whose part has a design hold is decided under **Part holds**, not listed twice.

## What each word means

| Word         | Means                                                                                                 |
| ------------ | ----------------------------------------------------------------------------------------------------- |
| **On hold**  | A request is waiting on you. Nobody works it.                                                         |
| **Canceled** | The MO is stopped for good and kept for records. A canceled MO never reads On hold.                   |
| **Obsolete** | You approved an obsolete request (or made the part obsolete yourself), so its open MOs were canceled. |

Obsolete parts aren't holds, so they don't appear here. To make one again, **Restore** the design part in the Design BOM.


---

# 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/admin-guide/holds.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.