DATA OPS

Snowflake Table Freshness Watchdog to Slack

Checks the last-loaded timestamp of your critical Snowflake tables on a schedule and posts a Slack alert the moment any table goes stale past its freshness SLA.

CategoryData Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEvery 15 minutes (business hours)
  • ActionQuery last-load timestamps per tableSnowflakeSnowflake
  • LogicCompute staleness vs per-table SLA
  • LogicStop if no tables are stale
  • OutputPost stale-table alert to SlackSlack

What it does

Runs a scheduled freshness sweep across a curated list of business-critical Snowflake tables. For each table it reads the most recent load timestamp, compares it against that table's allowed staleness window, and flags any table that has not been updated in time. Healthy runs stay quiet; only breaches trigger a Slack message naming the table, its expected cadence, and how many minutes late it is.

When to use it

Use this when downstream dashboards or models silently break because an upstream load failed and nobody noticed for hours. It gives data teams a single, low-noise heartbeat on the tables that actually matter.

How it works

  1. 1A schedule fires every 15 minutes during business hours.
  2. 2A Snowflake query pulls MAX load timestamps for each watched table from the metadata view.
  3. 3A logic step computes staleness per table and keeps only those past their SLA.
  4. 4A branch checks whether the breach list is empty and exits quietly if so.
  5. 5A Slack message lists each stale table with minutes-late and last-load time so an on-call analyst can act immediately.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.