> For the complete documentation index, see [llms.txt](https://help.urbanpiper.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.urbanpiper.com/business-manager/order-journey/understanding-cancelled-orders.md).

# Understanding Cancelled Orders

When an order is cancelled, the **Order Lifecycle** tab shows you who cancelled it, why, and how long after it was placed.

## How to Get to the Order Lifecycle Tab

1. Visit login.urbanpiper.com and log in using your credentials.
2. Click on the **Orders** section to view the list of orders.
3. Click on the order you want to explore to open it.
4. Click the **Order Lifecycle** tab.

## What You See on a Cancelled Order

A cancelled order gets:

* A **Cancelled** badge in the header.
* An **Order Cancelled** stage in the timeline.

The **Order Cancelled** stage shows:

* The cancellation reason.
* Who cancelled the order.
* How long after it was placed the order was cancelled.

![Order Lifecycle tab of a cancelled order showing the Cancelled badge, the Order Cancelled stage with its reason, and the failed Atlas to POS hop under Order Placement](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-2d10ae019f313591fef6d7d1735aff181ae81de5%2Forder-journey-06-cancelled-orders.gif?alt=media)

## Example

In this example:

* The POS cancelled the order 8 secs after it was placed.
* The reason given was "Location is not operationally open to take orders at the requested time."


---

# 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://help.urbanpiper.com/business-manager/order-journey/understanding-cancelled-orders.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.
