Read-only dbt Cloud workflow for reviewing recent account jobs and runs, including job recency, run status, failures, artifacts, and operational follow-up. It does not trigger jobs, cancel runs, mutate projects/environments/jobs, read credentials or service tokens, call Discovery or Semantic Layer APIs, or use arbitrary dbt API routes.

How it works 12 steps

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

Process (12 steps)

■ jobs_raw ?

■ runs_raw ?

■ jobs default

Apply default

■ runs default

Apply default

■ 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 ?

■ card to_summary

Format results as a summary card

Settings 6 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.

dbt cloud setting =

job limit setting = 15

run limit setting = 25

account id setting = 0

max length setting = 900