# Analyzing Individual Run Details

Investigate specific schedule executions to diagnose performance, troubleshoot issues, and verify data processing results.

{% hint style="info" %}
Access these details by selecting a Run ID from the [Run History table](/app-help/documentation/bolt/managing-schedules/viewing-run-log-history.md#run-history).
{% endhint %}

### Run Details Overview

Analyze your run execution through different visualization tools:

#### DAGs View

Visualize the execution flow of scheduled commands through a directed acyclic graph (DAG), showing:

* **Command dependencies -** Understand which models must complete before others can start
* **Execution order -** Track the sequence of operations to optimize pipeline flow
* **Process relationships -** Identify critical paths and potential parallelization opportunities

#### **Model Timeline**

Track the temporal sequence of model execution within your run:

* **Individual model execution times** - Spot which models are taking longer than expected
* **Parallel processing visualization** - See which models run simultaneously to maximize efficiency
* **Performance bottleneck identification** - Find slow-running models that delay your entire pipeline

{% @arcade/embed url="<https://app.arcade.software/share/fSI4ZiydwsvJGa9CYKMx>" flowId="fSI4ZiydwsvJGa9CYKMx" %}

{% hint style="info" %}
**Enhanced Navigation:** The model timeline includes **search and filter functionality** to quickly locate specific models by name, plus **zoom controls** to focus on specific time periods or view the entire run at once.
{% endhint %}

<figure><img src="/files/pcVyHvmAysP0aeV8DBPy" alt=""><figcaption></figcaption></figure>

***

### **Logs and Artifacts**

Explore additional metadata for each run ID, including a breakdown of run logs, source freshness, and artifacts.

{% @arcade/embed url="<https://app.arcade.software/share/TgVn754OtMX4OBm6Z9rV>" flowId="TgVn754OtMX4OBm6Z9rV" %}

#### Run Logs

The **Run Logs** section provides a detailed breakdown of each scheduled run, offering insights into execution status, performance, and any encountered issues. This section is divided into three tabs: **Summary**, **Console Logs**, and **Debug Logs**.

{% tabs %}
{% tab title="Summary" %}
**Overview**\
Displays high-level execution details for commands, showing the overall completion status, duration, and success metrics.

**Warnings and Errors**\
Lists any warnings or errors encountered during the run, such as deprecated configurations or unused paths.

**Suggested Actions**\
Recommendations to address identified warnings and errors, including updates for alignment with best practices.

**Use Case:**\
Quickly assess if the run was successful, spot any configuration issues, and take corrective actions.

<figure><img src="/files/jQhz6hcXW58iMLPNsE22" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Console Logs" %}
**Overview**\
Shows a line-by-line output of the command execution, starting with initialization and progressing through each execution step, including model or task processing times and completion summaries.

**Use Case**\
Ideal for reviewing the detailed flow of the run, identifying stages where issues may have occurred, and monitoring performance.

<figure><img src="/files/wL75l8wsdr2sByKYI001" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Debug Logs" %}
**Overview**\
Provides in-depth technical details, including system interactions, resource allocation, thread usage, and connection status to support troubleshooting.

**Use Case:**\
Best for advanced diagnostics and analyzing system performance, especially when investigating anomalies or unexpected behaviors.

<figure><img src="/files/9KJO2roJinc8A3e9IRsf" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Integration Logs" %}
**Overview**\
Provides in-depth logs of the payload sent to the connected integrations after the Bolt Run completed.

**Use Case:**\
Best for checking/validating the status of the integration sync, as well as the metadata being sent.

<div data-with-frame="true"><figure><img src="/files/FE0knCqjMDShYnimWPm6" alt=""><figcaption></figcaption></figure></div>
{% endtab %}
{% endtabs %}

Each tab gives a targeted view of run details, offering a complete understanding of pipeline performance.

#### Source Freshness

When your schedule includes the `dbt source freshness` command, you can:

* Monitor when each source table was last updated
* Track if data freshness meets your defined SLAs
* Identify stale or outdated data sources

<figure><img src="/files/pVvhrPvPYrwIiOO28vYW" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
💡 Learn how to configure source freshness in our [documentation](/app-help/documentation/bolt/managing-schedules/analyzing-run-details/configuring-source-freshness.md#how-to-configure-source-freshness).
{% endhint %}

#### Artifacts

The **Artifacts** section provides access to files that dbt generates after each run. These files help you analyze and troubleshoot your workflows:

#### SQL Files

* **Run SQL** - View the actual SQL statements executed during the run
* **Compiled SQL** - Examine the optimized SQL used in your data warehouse

#### Execution Metadata

* `manifest.json` - Shows project structure (models, sources, and tests)
* `catalog.json` - Contains schema information and column details
* `run_results.json` - Provides execution outcomes of dbt commands
* `sources.json` - Tracks source table metadata and freshness history

{% hint style="info" %}
Use these artifacts to verify execution details, troubleshoot issues, and audit your dbt workflow performance.
{% endhint %}

<figure><img src="/files/c5uZ6gvKE2eGXeYCHG04" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.paradime.io/app-help/documentation/bolt/managing-schedules/analyzing-run-details.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.