troubleshooting-dbt-job-errors

Diagnose and resolve dbt Cloud job failures through systematic root cause analysis.

Updated Jul 3, 2025
One-click install
npx skills add https://github.com/memadore/snowflake-dbt-demo --skill troubleshooting-dbt-job-errors-memadore
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting-dbt-job-errors
Source: https://github.com/memadore/snowflake-dbt-demo/tree/main/.agents/skills/troubleshooting-dbt-job-errors
Command: npx skills add https://github.com/memadore/snowflake-dbt-demo --skill troubleshooting-dbt-job-errors-memadore

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve failures in dbt Cloud or dbt platform jobs, especially when error messages are cryptic or failures are intermittent.

Core Features & Use Cases

  • Systematic Diagnosis: Guides users through identifying the root cause of dbt job failures.
  • Error Classification: Helps categorize errors into infrastructure, code/compilation, or data/test failures.
  • Tool Integration: Leverages MCP Admin API tools (list_jobs_runs, get_job_run_error) and dbt CLI commands.
  • Use Case: When a scheduled dbt job fails overnight, this Skill can be used to analyze the job logs, identify the specific error, and guide the user on whether to check warehouse connections, review recent code changes, or investigate failing data tests.

Quick Start

Use the troubleshooting-dbt-job-errors skill to diagnose a failed dbt job run by providing the job run ID.

Frequently Asked Questions about troubleshooting-dbt-job-errors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug a failed dbt Cloud job run?

To debug a failed dbt Cloud job run, gather job run information using MCP Admin API tools like list_job_runs and get_job_run_error, classify the failure into infrastructure, code, or data categories, and investigate root causes using dbt CLI commands.

What causes intermittent dbt job failures during scheduled runs?

Intermittent dbt job failures are caused by underlying infrastructure connection issues, compilation errors in recent code changes, or fluctuating data conditions failing tests. Systematic diagnosis isolates these root causes.

How do I classify dbt compilation errors versus data test failures?

Classify dbt compilation errors versus data test failures by analyzing job logs. Compilation errors stem from invalid SQL or model references, while data test failures indicate unexpected warehouse data values.

How do I retrieve error logs for a specific dbt job run ID?

Retrieve error logs for a specific dbt job run ID by using MCP Admin API tools like get_job_run_error. This fetches exact failure details to start the systematic troubleshooting workflow.

What is the best way to resolve cryptic dbt job error messages?

The best way to resolve cryptic dbt job error messages is prioritizing root cause analysis over quick fixes. Use dbt CLI and MCP tools to gather context, classify the error type, and implement a targeted fix.

What should I do when a dbt job failure remains unresolved after diagnosis?

When a dbt job failure remains unresolved after diagnosis, document the unresolved findings thoroughly. Record the classified error type, investigation steps taken, and root cause hypotheses for future analysis.