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

# Run Details

> Inspect a Bolt run: the pipeline, executed nodes, and model timeline, its succeeded/errors/skipped counts, and retry a failed run from failure or from scratch.

Open a run from a schedule's [run history](/products/bolt/managing-schedules/schedule-details#run-history) to see what happened: the pipeline, the executed nodes, timing, and per-command logs.

## Overview

The header shows the run number, its status, and when it ran. A metadata row shows the **date**, **duration**, **trigger**, **owner**, **branch and commit**, **SLA**, and **self-healing**. The stats panel shows the **Succeeded**, **Errors**, and **Skipped** counts.

## Run views

Switch between three views of the run:

* **Pipeline** — the commands as a DAG, each with its status.
* **Executed nodes** — the individual dbt™ objects (models, tests, and so on) the run built.
* **Model timeline** — models over time, to spot long-running or bottleneck models.

## Retry

If a run fails, click **Retry** to resume from the failed command or re-run every command. Each retry creates a new run and leaves the original intact. See [Retrying a run](/products/bolt/managing-schedules/retrying-a-run).

## Logs and artifacts

Each command in the run has an AI summary, full logs, and downloadable artifacts. See [Run logs and artifacts](/products/bolt/managing-schedules/run-logs-and-artifacts).


## Related topics

- [Schedule Details](/products/bolt/managing-schedules/schedule-details.md)
- [Debugging Failed Runs](/guides/paradime-101/running-dbt-in-production-with-bolt/debugging-failed-runs.md)
- [Retrying a Run](/products/bolt/managing-schedules/retrying-a-run.md)
- [Trigger PagerDuty Alarms](/products/bolt/creating-schedules/trigger-integrations/trigger-pagerduty-alarms.md)
- [Trigger incident.io Incidents](/products/bolt/creating-schedules/trigger-integrations/trigger-incident.io-incidents.md)