DATA OPS
BigQuery Scheduled-Query Failure Detector with PagerDuty Escalation
Polls the BigQuery scheduled-transfer run history every 15 minutes, finds runs that errored or were cancelled.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 minutes
- ActionList recent scheduled-query runsBigQuery
- LogicKeep only new FAILED/CANCELLED runs
- ActionOpen PagerDuty incident per failurePagerDuty
- OutputPost incident summary to SlackSlack
What it does
It watches BigQuery's Data Transfer Service run history for scheduled queries that finished in a FAILED or CANCELLED state and turns each new failure into a PagerDuty incident, so a silently broken nightly job pages someone instead of going unnoticed for a day.
When to use it
Use it when you run business-critical scheduled queries (revenue rollups, partner exports, ML feature tables) where a silent failure means downstream dashboards or pipelines serve stale or missing data. Best for teams that already route data on-call through PagerDuty.
How it works
- 1A schedule fires every 15 minutes.
- 2A BigQuery action lists transfer-config runs whose `endTime` falls in the window and reads each run's state and error status.
- 3A logic step keeps only runs in FAILED or CANCELLED state that haven't already been alerted.
- 4For each remaining failure, a PagerDuty action opens an incident titled with the query display name and the BigQuery error message.
- 5A Slack output drops a short summary into the data-eng channel linking the incident and the run in the BigQuery console.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.