DATA OPS
Stale Source Blast-Radius Watchdog for Downstream Tables
When a root source table in Snowflake lands late, calculates every downstream table that will inherit the staleness and notifies each dependent table's owner in Slack before…
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled source freshness check
- ActionRead root source table load timesSnowflake
- LogicIdentify breached root sources
- ActionExpand lineage to downstream ownersSnowflake
- OutputSlack heads-up to each affected ownerSlack
What it does
This workflow flips freshness monitoring from reactive to proactive. The moment a foundational source table misses its landing SLA in Snowflake, it expands the lineage graph forward to compute the full blast radius of downstream tables, then warns each affected owner that their data is about to be stale because of an upstream problem they did not cause.
When to use it
Use it for hub tables that fan out to dozens of marts. It prevents a wave of duplicate "my dashboard is wrong" tickets by getting ahead of the failure and naming the single upstream culprit to everyone affected.
How it works
- 1A schedule runs the source-table freshness check.
- 2It reads load timestamps for designated root source tables from Snowflake.
- 3A logic step identifies which roots breached their SLA.
- 4For each breached root it queries Snowflake lineage to enumerate all downstream dependent tables and their owners.
- 5It sends a targeted Slack heads-up to each downstream owner naming the late upstream source and expected impact.
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
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.