# Viewing Run History and Analytics

Bolt provides comprehensive tools for monitoring and analyzing your dbt™ schedules. This guide will walk you through viewing run logs, understanding the Bolt Schedules list, and exploring detailed analytics for your schedules.

**Estimated completion time:** 15 minutes

{% hint style="warning" %}

### Prerequisites

* Access to the [Bolt application](https://www.paradime.io/pricing) in Paradime
* At least one configured [Bolt schedule](https://docs.paradime.io/app-help/guides/paradime-101/running-dbt-in-production-with-bolt/creating-bolt-schedules)
  {% endhint %}

### What you'll learn

In this guide, you'll learn how to:

1. [Navigate the Bolt Schedules overview](#id-1.-bolt-schedules-overview)
2. [Access and interpret Bolt Schedule detail views](#id-2.-bolt-schedule-detail-views)
3. [Understand run history, logs, and artifacts](#id-2.1-run-history)

***

### 1. Bolt Schedules Overview

{% embed url="<https://youtu.be/gYOI1hqljzU>" %}

The Bolt home screen displays a summarized analysis of all your configured schedules, both UI-based and [YAML-based](https://docs.paradime.io/app-help/documentation/bolt/creating-schedules#yaml-based-schedules).  Here's what you can see at a glance:

<table><thead><tr><th>Field</th><th width="319">Description</th><th>Example</th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Name of the schedule</td><td><code>hourly scheduled run</code></td></tr><tr><td><strong>Status</strong></td><td>Current status of the schedule</td><td><code>Success</code></td></tr><tr><td><strong>Owner</strong></td><td>The schedule's owner (if configured)</td><td><code>john@acme.com</code></td></tr><tr><td><strong>Cron Description</strong></td><td>Human-readable description of the schedule's run time (UTC)</td><td>At 00:00, every day (UTC)</td></tr><tr><td><strong>Cron Configuration</strong></td><td>The cron syntax for the scheduled run</td><td>@daily</td></tr><tr><td><strong>Last Run</strong></td><td>Date and time of the most recent execution</td><td>August 22, 2024 at 5:00 PM PDT</td></tr><tr><td><strong>Next Run</strong></td><td>Anticipated date and time for the next execution</td><td>August 23, 2024 at 5:00 PM PDT</td></tr><tr><td><strong>Until Next Run</strong></td><td>Time remaining until the next scheduled runT</td><td>20 hours, 38 minutes, 52 seconds</td></tr><tr><td><strong>Trigger Type</strong></td><td>How the schedule is triggered (On schedule, On Run Completion)</td><td><code>standard</code></td></tr><tr><td><strong>On Completion Configuration</strong></td><td>Details of On Run Completion configuration (if applicable)</td><td><code>schedule base run in workspace irishtrooper on status passed, failed</code></td></tr></tbody></table>

### 2. Bolt Schedule Detail Views

The Bolt Schedule Detail View provides in-depth insights into individual dbt™ schedules, including configuration, run history, logs, and artifacts.

How to to access:

1. **Schedules Overview:** Navigate to the main page displaying all your configured schedules.
2. **Schedule Selection:** Click on a specific schedule name to view its detailed information and run history.

#### 2.1: Run History

{% embed url="<https://youtu.be/vjvDMwtTfWE>" %}

In the Run History section, you can view all executions of a specific scheduled run:

| Field                 | Description                                                   | Example                     |
| --------------------- | ------------------------------------------------------------- | --------------------------- |
| **Status**            | Status of the specific runID                                  | `Success`                   |
| **Trigger**           | If the runID was manually triggered manually or automatically | `Manual from john@acme.com` |
| **Branch and commit** | The branch name and commit SHA used when running the schedule | `main #ce34f`               |
| **Last Run**          | Date and time of when the runID was executed                  | `last month`                |
| **Duration**          | How long the run took to complete                             | `25 seconds`                |
| **RunID**             | Unique identifier of the run                                  | `13403`                     |

#### 2.2: Logs and Artifacts

{% embed url="<https://youtu.be/ynkNmpBIRW8>" %}

Every time a dbt™ command executes in a Bolt schedule, dbt Core™ generates a set of artifacts like manifest.json, catalog.json, run\_results.json, and sources.json. These tools help analyze, troubleshoot, and optimize your Bolt schedules.

**How to access:**

* Click on a specific run from a Bolt schedule's Run History
* Scroll down to Logs and Artifacts section

Let's explore the key components:

#### 2.3: Run Logs&#x20;

By clicking on a specific command executed in your bolt schedule (e.g., `dbt run`) you'll have access to various run logs:

| Run Log Type     | Description                                                                                                                                                                                                                                       | Use Case                                                            |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **Summary Logs** | [DinoAI-generated](https://docs.paradime.io/app-help/guides/paradime-101/getting-started-with-the-paradime-ide/dinoai-accelerating-your-analytics-engineering-workflow) overview of dbt command execution, including warnings and potential fixes | Quick assessment of run health and identification of common issues  |
| **Console Logs** | Detailed, chronological record of all operations                                                                                                                                                                                                  | Detailed troubleshooting and understanding of the execution process |
| **Debug Logs**   | Extensive details including system-level operations and dbt™ internals                                                                                                                                                                            | In-depth problem solving and performance tuning for complex issues  |

#### 2.4: Source Freshness

When your Bolt Schedule contains the command 'dbt source freshness', Paradime will provide the state of each of your sources. This helps you determine the status of your source data and whether it aligns with your SLAs.

<figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2Fz8kYlad2no4ukFKzMqqH%2Fimage.png?alt=media&#x26;token=595d5a6f-195b-49e4-89f2-98f1fc9f6375" alt=""><figcaption></figcaption></figure>

#### 2.5: Artifacts

During a Bolt schedule execution, dbt™ generates various files including run SQL files, compiled SQL files, manifest files, and JSON files. These artifacts provide insights into what was executed and how, enabling you to analyze the output of your dbt runs in detail.

<figure><img src="https://2337193041-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHET0AD04uHMgdeLAjptq%2Fuploads%2FhwL1D9N3WL2sOTR1YvN1%2Fimage.png?alt=media&#x26;token=9ec6776f-eed7-4eaf-a519-d812edf48ddc" alt=""><figcaption></figcaption></figure>

***

{% hint style="info" %}

### Related Documentation

* [View Bolt Run Logs](https://docs.paradime.io/app-help/documentation/bolt/managing-schedules/viewing-run-log-history)
* [Viewing Bolt Schedule Source Freshness ](https://docs.paradime.io/app-help/documentation/bolt/managing-schedules/analyzing-run-details/configuring-source-freshness)
  {% endhint %}

***

### Summary

You've learned how to navigate the Bolt Schedules overview, access detailed information about specific schedules, and interpret run history, logs, and artifacts. This knowledge will help you effectively monitor and analyze your dbt™ schedules, enabling you to optimize your data workflows and quickly troubleshoot any issues.

Next, we'll explore [how to set up notifications for your Bolt schedules](https://docs.paradime.io/app-help/guides/paradime-101/running-dbt-in-production-with-bolt/setting-up-notifications), ensuring you stay informed about the status of your data pipelines.


---

# 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/guides/paradime-101/running-dbt-in-production-with-bolt/viewing-run-history-and-analytics.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.