troubleshooting-dbt-job-errors

Diagnose dbt Cloud job failures using run logs, Admin API, git history, and data investigation.

9|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/mathisdrn/orca --skill troubleshooting-dbt-job-errors-mathisdrn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshooting-dbt-job-errors
Source: https://github.com/mathisdrn/orca/tree/main/.agents/skills/troubleshooting-dbt-job-errors
Command: npx skills add https://github.com/mathisdrn/orca --skill troubleshooting-dbt-job-errors-mathisdrn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When a dbt Cloud or dbt platform job fails, error messages are often unclear and failures can be intermittent, making root cause analysis slow and error-prone. This Skill provides a systematic workflow to diagnose failures instead of guessing or blindly modifying tests. ## Core Features & Use Cases - Structured Diagnosis Workflow: Classifies failures into infrastructure, code/compilation, or data/test errors, then applies targeted investigation steps for each type. - Multi-Source Investigation: Uses the dbt MCP Admin API (list_jobs_runs, get_job_run_error), git history review, dbt CLI commands (parse, compile, show), and compiled test SQL to trace root causes. - Resolution Discipline: Enforces creating a fix branch, adding unit or data tests to prevent recurrence, and documenting unresolved findings with an investigation template. - Use Case: A nightly dbt Cloud job fails on a uniqueness test. The Skill pulls the run error via the Admin API, compiles the failing test's SQL, queries the underlying data with dbt show, and identifies that a recent upstream change introduced duplicate keys. ## Quick Start Diagnose why my dbt Cloud job 12345 failed last night and find the root cause.

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 troubleshoot a failed dbt Cloud job?▼

Start by pulling the run history with list_jobs_runs and error details with get_job_run_error from the dbt Admin API. Then classify the failure as infrastructure, code/compilation, or data/test, and follow the targeted investigation steps for that error type.

How to investigate a failing dbt test?▼

Compile the failing test with dbt compile to get its SQL, then run that query with dbt show to inspect the actual failing rows. Compare results against recent git changes to determine whether a transformation change or upstream data shift caused the failure.

Can I diagnose dbt job failures without the dbt MCP server?▼

Yes, request the debug logs and run_results.json artifact from the user via the dbt Cloud artifact URL. You can then classify the error and use the dbt CLI and git history locally to continue the investigation.

Should I modify a failing dbt test to make it pass?▼

No, a failing test is evidence of an underlying problem and changing it hides the issue. Investigate the root cause first, fix the actual problem, and add a unit or data test to prevent recurrence.

What should I do when a dbt job failure root cause is not found?▼

Document the investigation using the findings template instead of guessing at a fix. Record which tools were used, hypotheses tested, observed patterns, and suggested next steps, then commit the document to the repository.