Bruin Cloud Step 3 of 5

Operate Bruin Cloud From the Terminal

Guide overview
  1. Connect the CLI to Bruin Cloud5 min
  2. Inspect Pipelines, Runs, and Assets4 min
  3. 3Diagnose and Recover From Failures4 min
  4. 4Trigger Runs and Backfills5 min
  5. 5Chat With Agents and Track Cost4 min
PreviousInspect Pipelines, Runs, and AssetsNextTrigger Runs and Backfills

1) Diagnose the latest failure

Instead of listing runs and hunting for the bad one, ask for the diagnosis directly:

bruin cloud runs diagnose --project-id "$PID" --pipeline <pipeline-name> --latest

--latest targets the most recent run of the pipeline and prints its errors and failed checks in one place. If you already have a specific run ID, point at it instead:

bruin cloud runs diagnose --project-id "$PID" --run-id <run-id>

This is the fastest way from "a pipeline is red" to "here is the asset and the error message."

Sign up to our newsletter

Practical updates on open-source data pipelines, AI analysts, governance, and what we are shipping at Bruin.

The signup form is hosted by Brevo. Accept cookies to load it.