DATA OPS
dbt Freshness Sentinel: Pause Dashboards on Stale Downstream Tables
On a schedule, checks the load timestamps of critical Snowflake marts and, when any model exceeds its freshness SLA, flips a dashboard kill-switch flag and posts an outage notice…
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 30 min during business hours
- ActionQuery max load timestamp per watched martSnowflake
- LogicCompare each table's age to its freshness SLA
- ActionFlip is_paused flag in dashboard control tableSnowflake
- OutputPost outage notice naming stale tables to SlackSlack
What it does
Runs a freshness audit against a curated list of downstream Snowflake marts (revenue, pipeline, exec KPIs). For each table it compares the latest `_loaded_at` against a per-table SLA you define. If any table is past its threshold, it marks those dashboards as paused by updating a control table and broadcasts a clear outage message to the data consumers' Slack channel.
When to use it
Use when business dashboards read directly from a handful of high-visibility marts and a silent upstream failure would put wrong numbers in front of leadership. This is the guardrail that turns "the dashboard is wrong" into "the dashboard says it's paused."
How it works
- 1A schedule fires every 30 minutes during business hours.
- 2A Snowflake query pulls the max load timestamp for each watched mart.
- 3A logic step compares each table's age against its SLA and collects the stale ones.
- 4If the stale set is non-empty, a Snowflake update flips an `is_paused` flag in the dashboard control table.
- 5A Slack message names the stale tables, their lag, and the affected dashboards, then links the runbook.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 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.