> ## 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 Logs and Artifacts

> Inspect each command in a Bolt run: the DinoAI summary, full debuggable logs, generated artifacts like Run SQL, Compiled SQL, and JSON, plus source freshness.

The **Logs & artifacts** section of a [run](/products/bolt/managing-schedules/run-details) lets you inspect each command. Select a command from the steps list, then choose a tab.

## DinoAI summary

An AI-generated summary of the command's logs, highlighting what ran, what passed, and any warnings or errors. It is the fastest way to understand a command without reading the full log.

## Logs

The full command logs. You can:

* **Search** the logs.
* Filter by pass or fail.
* Toggle **Debug logs** for verbose output.
* **Download** the logs.

## Artifacts

The files the command generated, grouped into:

* **Run SQL** — the executed SQL for each model.
* **Compiled SQL** — the compiled SQL before execution.
* **Other** — JSON artifacts such as `manifest.json` and `run_results.json`.

Search the file list and click **View** to open any file.

## Source freshness

If the run includes a `dbt source freshness` command, the **Source freshness** tab shows the state of each source: fresh, warn, stale, or error. If the run has no source freshness command, add one to the schedule's [commands](/products/bolt/creating-schedules/command-settings/index) to track how up-to-date your sources are.


## Related topics

- [Run Details](/products/bolt/managing-schedules/run-details.md)
- [Viewing Run History and Analytics](/guides/paradime-101/running-dbt-in-production-with-bolt/viewing-run-history-and-analytics.md)
- [Debugging Failed Runs](/guides/paradime-101/running-dbt-in-production-with-bolt/debugging-failed-runs.md)
- [Bolt](/developers/python-sdk/modules/bolt.md)
- [Azure DevOps](/products/bolt/ci-cd/turbo-ci/azure-devops.md)