DATA OPS
dbt Freshness SLA Watcher: Pause Dependent Models on Late Loads
Checks the freshness of upstream source tables on a schedule, and when a load lands past its SLA it disables the downstream dbt models that depend on it and posts a notice…
How it runs
The automated pipeline, trigger to output.
- TriggerEvery 30 minutes (schedule)
- ActionQuery MAX(loaded_at) per source tableSnowflake
- LogicFlag sources past their SLA threshold
- ActionPause dependent dbt models via dbt Cloud APIHTTP webhook
- OutputPost late-source + held-model notice to SlackSlack
What it does
This watcher polls your warehouse for the last-loaded timestamp of each tracked source table, compares it against a per-source SLA, and when a source is late it proactively pauses the dependent dbt transforms instead of letting them run on stale inputs. Every action is announced in Slack with the offending source, how late it is, and exactly which models were held.
When to use it
Run it when an upstream extract feeds a chain of dbt models and you cannot tolerate transforms silently computing on yesterday's data. It is built for teams who would rather skip a run than publish wrong numbers.
How it works
- 1A schedule fires every 30 minutes.
- 2Query Snowflake for MAX(loaded_at) per tracked source table.
- 3A logic step flags any source where the gap exceeds its SLA threshold.
- 4For each breached source, call the dbt Cloud API via webhook to set its dependent models to a paused/skip state.
- 5Post a Slack message listing each late source, its lateness, and the models that were held.
- 6Output a structured summary record of the run for the audit trail.
Set it up
What you configure once, before turning it on.
- 1Connect SnowflakeWarehouses, queries, shares.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 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.