> 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-muted-events.md).

# Understanding Muted Events in the Order Lifecycle

On the **Order Lifecycle** tab, some events appear greyed out. These are called muted events. This article explains when you will see them and what they mean.

## 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.

## When Events Are Muted

You will see muted (greyed-out) events on an order in two cases.

![Order Lifecycle tab with Order Ready, Order Dispatch and Rider Status greyed out, and the expanded Order Completion showing a muted Atlas to POS hop](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-ffdab395d37820c2c47ac6f61febf462264d8016%2Forder-journey-03-muted-events.gif?alt=media)

### 1. The Event Never Happened

Some steps are muted because the event never took place.

In this example, the store never marked the order as **Order Ready** or **Dispatched**, so those two steps stay greyed out.

Further, UberEats did not send any rider updates for this order. Hence, **Rider Status** is muted too.

### 2. The Destination System Does Not Support the Event

Some hops are muted because the destination system cannot accept the event.

In this example, UberEats sent **Completed** to Atlas, but the Atlas → POS hop could not be sent on, as the destination POS does not support accepting this status.

The muted hop shows the message: **Completed updates are not supported by this POS.**

## How to Read a Muted Event

A muted event is not a failure. It tells you either that the event did not happen, or that the destination system does not support it. To identify real failures, see [Spotting Failed Hops at a Glance](https://help.urbanpiper.com/business-manager/order-journey/spotting-failed-hops-at-a-glance.md).


---

# 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-muted-events.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.
