DATA OPS
BigQuery Scheduled-Query Retry with Backoff Self-Heal
When a BigQuery scheduled query fails, this workflow inspects the error, retries transient failures with exponential backoff.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled query run finishes FAILEDBigQuery
- LogicClassify error: transient vs permanent
- ActionRe-run transfer config with backoffBigQuery
- LogicRetry succeeded or budget exhausted?
- ActionPost recovery note on successDiscord
- OutputOpen Trello incident card on failureTrello
What it does
Catches a failed BigQuery scheduled-query run, classifies the failure, and automatically re-runs transient failures up to three times with growing wait intervals. Permanent failures (bad SQL, missing table, permission denied) skip retries and go straight to an incident card so engineers do not waste a retry budget on something that cannot self-heal.
When to use it
Use it for production scheduled queries that occasionally hit quota limits, slot contention, or brief source-table locks — failures that almost always succeed on a second attempt. It removes the 2 a.m. pager noise for blips while still surfacing the real breakages.
How it works
- 1A BigQuery transfer-run completion event fires when a scheduled query ends in FAILED state.
- 2A logic branch reads the error class: transient (rate-limit, backendError, resourcesExceeded) vs permanent.
- 3For transient errors, the workflow triggers a manual re-run of the transfer config, then waits and re-checks status, escalating the backoff on each loop up to three tries.
- 4If a retry succeeds, it posts a short recovery note to Discord and stops.
- 5If retries are exhausted or the error was permanent, it opens a Trello incident card with the query name, error text, and run history.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect DiscordCommunity channels + voice + bots.
- 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
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 orphan model detector with Linear cleanup tickets
Scans your dbt manifest for models that no other model, exposure, or BI tool consumes.
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.
Backfill Missing Owner Labels on BigQuery Scheduled Queries
Finds scheduled queries with no owner label, infers the likely owner from creator metadata and target-table lineage, proposes a label.
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.
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…
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.