DATA OPS

BigQuery Failure Auto-Remediation via bq CLI Script

On a scheduled-query failure, runs a guarded shell remediation script (bq CLI) to fix common issues like stale views or missing scratch tables.

CategoryData Ops
Enginesim
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled query failure eventGoogle BigQueryBigQuery
  • LogicMatch error to known remediation playbook
  • ActionRun bq CLI fix in guarded shellShell
  • ActionRe-run query and verify statusGoogle BigQueryBigQuery
  • OutputLog transcript and outcome to TrelloTrelloTrello

What it does

Applies scripted fixes for the handful of failure modes your team already knows how to remediate by hand. A shell step runs `bq` CLI commands — recreate a missing staging table, refresh a materialized view, or grant a known service-account role — then re-triggers the query and checks whether the fix held.

When to use it

Use it when the same two or three failures keep paging on-call and the manual fix is always identical. Codifying that fix into a guarded script turns a 15-minute interruption into a hands-off recovery, while still recording exactly what was changed.

How it works

  1. 1A BigQuery scheduled-query failure event triggers the run.
  2. 2A logic step matches the error fingerprint against a known-remediation playbook and exits to manual handling if there is no match.
  3. 3A shell action runs the matching `bq` CLI remediation commands inside the guarded sandbox.
  4. 4The workflow re-runs the scheduled query and reads the new status.
  5. 5It writes the full command transcript and final outcome to a Trello card — closing it automatically if the fix succeeded, leaving it open and labeled if not.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect BigQueryDatasets, queries, schemas.
  2. 2
    Connect ShellRun sandboxed commands inside the workspace.
  3. 3
    Connect TrelloKanban boards for everything.
  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.