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.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled query failure eventBigQuery
- LogicMatch error to known remediation playbook
- ActionRun bq CLI fix in guarded shellShell
- ActionRe-run query and verify statusBigQuery
- OutputLog transcript and outcome to TrelloTrello
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
- 1A BigQuery scheduled-query failure event triggers the run.
- 2A logic step matches the error fingerprint against a known-remediation playbook and exits to manual handling if there is no match.
- 3A shell action runs the matching `bq` CLI remediation commands inside the guarded sandbox.
- 4The workflow re-runs the scheduled query and reads the new status.
- 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.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect TrelloKanban boards for everything.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Data Ops workflows
Weekly BigQuery Cost Trend Sheet and Exec Digest
Compiles week-over-week BigQuery scheduled-query cost by owner and dataset into a Google Sheet with trend columns.
Daily BigQuery Scheduled-Query Cost Attribution to Owners
Each morning, totals the prior day's on-demand bytes-billed per scheduled query, maps each query to its owner from a label, and posts a per-owner cost leaderboard to Slack.
BigQuery Per-Team Budget Breach Alert to PagerDuty
Tracks month-to-date BigQuery scheduled-query spend per team and, when a team crosses its monthly budget, pages the team's on-call in PagerDuty and snapshots the spend breakdown…
dbt source freshness watcher with severity-routed alerts
Checks Snowflake loaded-at timestamps against each dbt source's freshness SLA, then routes warnings to Slack and hard breaches to a PagerDuty incident so stale data never…
dbt orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
Raw Sensor Telemetry Archive to BigQuery
Captures every incoming building sensor reading via webhook, normalizes the payload into a consistent schema.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.

Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.
