Use “dbt Cloud run health brief” in Recued. It provides a read-only dbt Cloud workflow for reviewing recent account jobs and runs, including job recency, run status, failures, artifacts, and operational follow-up.

How it works 11 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (11 steps)

◆ jobs_raw recued-core.dbt-cloud.job.search

Search job on dbt cloud

◆ runs_raw recued-core.dbt-cloud.run.search

Search run on dbt cloud

■ defaults defaults

Apply defaults

■ job_count count

Count items in jobs

■ run_count count

Count items in runs

■ job_rows slice

Take a subset of

■ run_rows slice

Take a subset of

■ job_table to_table

Format results as a data table

■ run_table to_table

Format results as a data table

✦ summarize core.ai.summarize

AI generates a concise summary

■ card to_summary

Format results as a summary card

▼

Output

summary card

table run_table

table job_table

Settings 5 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Summarize current dbt Cloud job and run health. Call out failed, cancelled, long-running, queued, or stale runs, useful artifacts, likely owner follow-ups, and missing context. Do not invent run causes or model failures that are not in the dbt Cloud payload.

job limit setting = 15

run limit setting = 25

account id setting = [object Object]

max length setting = 900