# Runs

A run is a single execution of an automation. Every run is captured for audit and debugging.

## What a Run Records

Each run records enough data to trace what happened from trigger to final outcome.

| Field              | Description                                                                    |
| ------------------ | ------------------------------------------------------------------------------ |
| **Status**         | Pending, Running, Completed, Failed, Suspended, or Cancelled.                  |
| **Initiator**      | Who or what started the run — a user, an event handler, a webhook, a schedule. |
| **Trigger output** | The data emitted by the trigger.                                               |
| **Steps**          | For each step: status, input, output, error, duration, retry count.            |
| **Version**        | Which published version of the automation was used.                            |

## Run Detail View

Open a run from the **Runs** view on the automation. The run detail page replays the automation on the canvas with each step coloured by status. Click a step to view the resolved settings and output for that run.

## Versioning and Runs

A run always completes on the version of the automation that was live when the run started. Publishing a new version does not affect runs that are already in progress.

## Retention

Run data is retained according to the `AuditLogRetentionDays` setting. See [Configuration](/umbraco-automate/getting-started/configuration.md) for details.

## See Also

* [Reviewing Runs](/umbraco-automate/backoffice/runs.md)
* [Versioning](/umbraco-automate/concepts/versioning.md)


---

# Agent Instructions: 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:

```
GET https://docs.umbraco.com/umbraco-automate/concepts/runs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.