> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oviond.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Run history

> See every past run of a project's automations and its status.

The **Automation History** page lists every run recorded for a project — across all of its automations, and including both scheduled deliveries and test sends. Open it from an automation's **Executions** action, or from the row menu. The page lives at `/automations/:project_id`.

Each row shows the run's name, **Source** (**Scheduled** or **Test**), the time it sent, its status, the report **Type**, and the **Date range** it covered. Test runs are also tagged with a **Test** badge. You can search by name and filter by report type, and the list is paginated.

## Status values

| Status      | Meaning                                                                                               |
| ----------- | ----------------------------------------------------------------------------------------------------- |
| **Success** | The run rendered and sent.                                                                            |
| **Failed**  | The run errored — typically a rendering or delivery problem. The error detail is stored with the run. |
| **Skipped** | The run was skipped (for example, the automation was paused when it was due).                         |

## When to check history

* **Debugging a missed delivery** — confirm a scheduled run actually fired and whether it succeeded or failed.
* **Verifying a test** — a test send shows up here as a **Test** row right after you trigger it.
* **Auditing** — confirm an end-of-month report went out on time.

## Endpoint

The history is served by `GET /v1/automations/:project_id/history` — note that it's scoped by **project**, not by a single automation id. It aggregates the runs of every automation attached to that project into one timeline and is paginated via `page` and `limit`.

<Note>
  Archiving a run from the history list removes the underlying report snapshot for that run, not the automation itself. The automation keeps running on its schedule.
</Note>