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

# Run history

> Monitor automation performance, view run details, and diagnose failures.

Every automation tracks a complete history of its runs — when they started, whether they succeeded or failed, how long they took, and what each action did. Use the run history tab to monitor performance and troubleshoot issues.

## View run history

<Steps>
  <Step title="Open the automation">
    Click any automation on the automations list page.
  </Step>

  <Step title="Go to the Run history tab">
    Click the **Run history** tab at the top of the editor.
  </Step>
</Steps>

The run history tab has two sections: a performance graph at the top and a table of individual runs below.

## Performance graph

The graph shows successful and failed runs over time. Toggle between three time periods:

* **24h** — the last 24 hours
* **7 days** — the last week
* **30 days** — the last month

Below the graph, summary stats show:

* **Total** — total number of runs in the period
* **Success** — number of successful runs
* **Error rate** — percentage of runs that failed
* **Avg duration** — average time to complete a run

## Run table

The table lists each individual run with the following columns:

* **Status** — whether the run is active, finished (successful), failed, or waiting
* **Triggered at** — when the run started
* **Triggered for** — the record that triggered the automation
* **Duration** — how long the run took to complete
* **Actions performed** — how many actions ran

Click **View actions** on any row to see what happened in each step.

### Sort runs

Click the column headers to sort by **Status** or **Triggered at**. Runs are sorted by most recent by default.

## View run details

<Steps>
  <Step title="Open run history">
    Go to the automation's **Run history** tab.
  </Step>

  <Step title="Click View actions">
    Click **View actions** on the run you want to inspect. A panel opens showing each action that ran.
  </Step>

  <Step title="Review each action">
    Each action shows its status (finished, failed, active, or waiting), linked records, notes about what happened, and any errors.
  </Step>
</Steps>

## Stop a running automation

If an automation is currently running and you need to stop it:

<Steps>
  <Step title="Find the active run">
    Open the automation's **Run history** tab and locate the run with an **Active** or **Waiting** status.
  </Step>

  <Step title="Click Stop run">
    Click the stop button on the run row. Confirm that you want to stop it.
  </Step>
</Steps>

The run is marked as failed and any remaining actions are skipped.

## Activity chart on the list page

The automations list page shows an aggregate activity chart across all your automations. This chart displays the last 30 days of runs, with green bars for successful runs and red bars for failures.

Each automation row also shows:

* **Status** — the result of the most recent run and when it happened
* **Total runs** — total runs in the last 7 days
* **Success rate** — percentage of successful runs in the last 7 days

## FAQ

<AccordionGroup>
  <Accordion title="Can I retry a failed run?">
    Yes. Failed runs can be retried within 24 hours. The retry picks up from the last failed action.
  </Accordion>

  <Accordion title="How long is run history kept?">
    Run history is kept indefinitely. You can delete all run history from the automation's **Settings** tab under **Danger zone**.
  </Accordion>

  <Accordion title="Why does a run show as 'waiting'?">
    A run shows as waiting when it has reached a [Wait](/platform/automations/actions#wait) action and is paused for the configured duration. It will resume automatically.
  </Accordion>
</AccordionGroup>