For dbt pipelines

Your dbt tests just failed.
Here's why.

DataPipe Doctor reads the failing model's SQL, its lineage, and sample bad rows — then explains the root cause in plain English instead of leaving you to trace it by hand.

Free to start · No credit card required

not_null_orders_amountFailed

AI root cause

The orders model LEFT JOINs payments, so orders without a successful payment get a null amount.

How it works

From a red test to a fix, in three steps

1

Connect your dbt project

A one-line CLI wraps your existing dbt build/test command — no config rewrite.

2

Push run results

The CLI reads dbt's own manifest and run results and pushes them after every run.

3

Get the root cause

Failing tests are explained in plain English, grounded in your actual SQL and lineage.

Reads your real lineage

Parses dbt's own manifest.json — no separate SQL parser to keep in sync with your project.

Explains, doesn't just alert

An LLM reads the failing model's SQL, its parents, and sample bad rows to write the actual root cause.

Catches flaky tests

Tracks pass/fail across runs and flags tests that fail intermittently, not just the ones failing right now.

Stop tracing failures by hand

Connect a project and see a real root-cause explanation on your very next failing test.

Get started free