> 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/spotting-failed-hops-at-a-glance.md).

# Spotting Failed Hops at a Glance

The **Order Lifecycle** tab is designed so you can find where an order failed without searching. Every hop carries a status indicator, and the failed status opens automatically.

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

## Hop Status Indicators

Every hop carries a status indicator:

* **Hop completed:** The hop went through.
* **Hop failed:** The hop did not go through.
* **Hop did not happen:** The hop never took place.

## How Failures Are Shown

By default, the view expands the status where the failed hop has occurred and shows a brief failure reason.

![Order Lifecycle tab with Order Placement expanded, showing a failed Atlas to POS hop with the reason Pos push failed and 4 attempts, followed by the list of attempts](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-cf6a3338f88704322c07634d3e5eeb5bb4b91fb8%2Forder-journey-05-spot-the-failure.gif?alt=media)

## How to Debug a Failed Hop

1. On the **Order Lifecycle** tab, find the status that is expanded by default. It contains the failed hop and a brief failure reason.
2. Click the failed hop to open its details panel.
3. Review the details to find the exact cause of the failure.

## Retries Before a Failure

If a hop fails, Atlas retries it to prevent the failure.

In this example, the Atlas → POS hop shows **POS Push Failed** after Atlas retried pushing it 4 times. To review each attempt, see [Viewing Retries for an Event, Attempt by Attempt](https://help.urbanpiper.com/business-manager/order-journey/viewing-retries-for-an-event.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/spotting-failed-hops-at-a-glance.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.
