> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-automate/18.latest/backoffice/runs.md).
# Review Runs
Every execution of an automation produces a **run** record. Use the **Runs** view to find a specific run and inspect its data step by step.
## Find a Run
1. Open the automation in the tree.
2. Switch to the **Runs** tab.
3. Scroll or page through the list of runs, most recent first.
The runs list view.
## Inspect a Run
Click a run to open the run detail view. The canvas replays the automation with each step coloured by execution status:
| Colour | Status |
| ------ | -------------------------------------------------------- |
| Grey | Pending — not yet run |
| Blue | Running |
| Green | Completed |
| Red | Failed |
| Yellow | Waiting for input (for example, an approval) or sleeping |
Click a step to open its data panel.
## Read Step Data
The data panel shows three sections for the selected step:
| Section | Contents |
| ------------ | -------------------------------------------------------------------- |
| **Settings** | The resolved settings used for this run, with all bindings replaced. |
| **Output** | The data the step produced, available to downstream bindings. |
| **Error** | The exception message and category if the step failed. |
## Retention
Old run data is purged based on the `AuditLogRetentionDays` setting. See [Configuration](/umbraco-automate/18.latest/getting-started/configuration.md).
## See Also
* [Runs](/umbraco-automate/18.latest/concepts/runs.md)
* [Versioning](/umbraco-automate/18.latest/concepts/versioning.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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.umbraco.com/umbraco-automate/18.latest/backoffice/runs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.