> 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/viewing-retries-for-an-event.md).

# Viewing Retries for an Event, Attempt by Attempt

When a hop fails, Atlas retries it automatically. The **Order Lifecycle** tab lets you see every attempt, so you can understand what happened before the hop finally went through.

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

## How Retries Work

When a hop fails, Atlas retries it automatically. If a later attempt goes through, the hop shows as successful, along with how many attempts it took.

In this example, the Atlas → POS hop shows **3 attempts**.

## How to View the Attempts

1. On the **Order Lifecycle** tab, click **View Details** on the status you want to explore.
2. Click the hop to open its details panel.
3. Review the attempts listed in the panel. The attempts are listed newest first, and each one has its own timestamp.
4. Expand an attempt to see its own request and response.

![Order Placement details panel showing the Atlas to POS hop with 3 attempts listed newest first, and one attempt expanded to show its trace ID and request payload](https://289760566-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxCNwyBrdk3hWPYP9o2S%2Fuploads%2Fgit-blob-319cf25a6bcd12f8d7c197a9ce9efae4a5053bb8%2Forder-journey-04-view-retries.gif?alt=media)

## What Each Attempt Shows

Each attempt lists its:

* Method
* URL
* Status code
* Timestamp

Each attempt can be expanded to show its own request and response.


---

# 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/viewing-retries-for-an-event.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.
