DATA OPS
Auto-release quarantined BigQuery views when backfill lands
Polls quarantined tables for the missing partition and, the moment a complete backfill is detected.
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 5 min while quarantine is active
- ActionRead quarantine ledger and saved view SQLPostgres
- ActionCheck awaited partition existence and row countBigQuery
- LogicConfirm backfill is present and complete
- ActionRestore original view definitions to lift quarantineBigQuery
- OutputMark ledger resolved and post all-clear to SlackSlack
What it does
This is the recovery half of the watchdog. It tracks which tables and views are currently quarantined, repeatedly checks BigQuery for the late partition to arrive, validates that the row count clears a minimum-completeness threshold, then restores the saved original view definitions and clears the quarantine flag.
When to use it
Use it alongside a quarantine workflow so operators never have to manually un-break dashboards after a delayed ingest finally catches up. Ideal when backfills land at unpredictable times overnight.
How it works
- 1A schedule fires every 5 minutes while any view is in quarantine.
- 2A Postgres action reads the quarantine ledger to get the tables and saved original view SQL.
- 3A BigQuery action checks the awaited partition's existence and row count.
- 4A logic step confirms the partition is present and complete enough to release.
- 5A BigQuery action runs `CREATE OR REPLACE VIEW` with the original definitions to lift quarantine.
- 6A Postgres action marks the ledger rows resolved, and a Slack message posts the all-clear with recovery latency.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.