DATA OPS

BigQuery Failure Triage Agent with Root-Cause Card

An agent investigates a failed BigQuery scheduled query by pulling the error, the SQL, and recent schema changes.

CategoryData Ops
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled query failure eventGoogle BigQueryBigQuery
  • ActionGather SQL, error, and table metadataGoogle BigQueryBigQuery
  • LogicReason over evidence for root cause
  • ActionCreate Trello root-cause incident cardTrelloTrello
  • OutputAlert on-call in Discord with card linkDiscordDiscord

What it does

Instead of just forwarding a cryptic BigQuery error, an agent gathers the context a human would: the failing SQL, the exact error and stack, recent changes to referenced tables, and whether other queries on the same source also broke. It synthesizes this into a readable root-cause hypothesis and suggested fix, attached to a Trello incident card.

When to use it

Use it when scheduled-query failures land on a rotating on-call who lacks deep context on every pipeline. The agent does the first 20 minutes of triage so the responder opens the card already knowing the likely cause and next step.

How it works

  1. 1A BigQuery scheduled-query failure event starts the run.
  2. 2The agent fetches the error detail, the rendered query SQL, and metadata for every referenced table.
  3. 3It checks recent schema or partitioning changes and looks for correlated failures across related transfer configs.
  4. 4The agent reasons over the evidence to produce a ranked root-cause hypothesis and a concrete remediation suggestion.
  5. 5It creates a Trello incident card with the analysis, evidence links, and a severity label, then drops a thread alert in Discord pointing on-call to the card.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect TrelloKanban boards for everything.
  3. 3
    Connect DiscordCommunity channels + voice + bots.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.