DATA OPS
Snowflake Load-Window SLA Watchdog
Checks every table's most recent load time against its expected freshness window and alerts the data team in Slack the moment a table goes stale.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: every 10 minutes
- ActionQuery Snowflake load history + SLA registrySnowflake
- LogicCompute lag, keep tables past their freshness window
- LogicExit quietly if no breaches
- OutputPost ranked breach list to Slack, tag ownersSlack
What it does
Every few minutes it scans a registry of tracked Snowflake tables, compares each table's last successful load timestamp against its declared freshness SLA, and flags any table whose data is older than its allowed window. Healthy tables stay silent; breaches go to Slack with the table name, how far past SLA it is, and the named owner.
When to use it
Use it when downstream dashboards or models depend on tables loading on a schedule and a silent missed load currently goes unnoticed until someone complains. It turns "the numbers look wrong" into a proactive page.
How it works
- 1A schedule fires the run on a fixed cadence (for example every 10 minutes).
- 2It queries Snowflake's load history and the freshness-SLA registry to get last-load time and the allowed window per table.
- 3A freshness check computes lag per table and keeps only those past their window.
- 4If nothing is stale the run ends quietly; otherwise it formats a breach summary.
- 5It posts the ranked breach list to the data-ops Slack channel, tagging each table's owner.
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.