Skip to main content
The Logs & artifacts section of a run 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, colour coded the same way they are in the IDE terminal, in both the light and dark themes. This covers dbt™ and dbt Fusion output as well as anything else a command prints, including tools like edr, ruff, and uv. Because dbt™ colours only the status token on each line, Paradime also tints each line by its parsed status: a red-tinted ERROR, an amber WARN, and accent bars on OK and SKIP. The toolbar carries the totals, for example 12 pass · 1 warn · 1 error · 2 skip · 16 total. You can:
  • Search the logs.
  • Filter by pass or fail.
  • Toggle Debug logs for verbose output: the command’s logs/dbt.log file, which you can also download through the Bolt API.
  • 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 to track how up-to-date your sources are.