DATA OPS
BigQuery freshness watchdog with downstream view quarantine
Checks expected partitions against an SLA clock on a schedule, and when a daily partition lands late it flips the dependent BigQuery views into a quarantine state and posts…
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 15 min during ingestion window
- ActionRead latest partition per table from INFORMATION_SCHEMABigQuery
- LogicCompare arrival vs SLA, isolate breached tables
- ActionCREATE OR REPLACE VIEW to quarantine downstream viewsBigQuery
- OutputPost breach + affected views to data on-call SlackSlack
What it does
It watches the latest landed partition for each tracked BigQuery table, compares its arrival time to a per-table freshness SLA, and when a partition is missing past its deadline it quarantines every downstream view that reads from that table. Quarantine swaps the view definition to return zero rows plus a `_quarantined` flag, so dashboards visibly break instead of silently serving stale numbers.
When to use it
Use it when late-arriving ingestion silently poisons executive dashboards and you would rather fail loud than serve yesterday's data. Best for daily-partitioned fact tables feeding revenue, ops, or marketing reporting.
How it works
- 1A schedule fires every 15 minutes during the ingestion window.
- 2A BigQuery query reads `INFORMATION_SCHEMA.PARTITIONS` for each tracked table and returns the newest partition timestamp.
- 3A logic step compares each timestamp to the table's SLA deadline and isolates the breached tables.
- 4For breached tables, a BigQuery action runs `CREATE OR REPLACE VIEW` to quarantine the dependent views.
- 5A Slack message posts the breach list, affected views, and minutes-late to the data on-call channel.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.