DATA OPS

Daily Digest of Stale Dashboards to Their Owners

Each morning it finds every dashboard whose underlying dbt models did not refresh successfully overnight and sends each owner a personalized email listing exactly which of their…

CategoryData Ops
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerMorning schedule fires
  • ActionQuery Snowflake for stale models + dependent dashboardsSnowflakeSnowflake
  • LogicGroup stale dashboards by owner, skip empty
  • ActionEmail each owner their stale-dashboard digestGmailGmail
  • OutputPost roll-up count to SlackSlack

What it does

Gives dashboard owners a single morning heads-up about which of their assets are stale. It joins last-successful-build times for each dbt model to the dashboards that consume them, then groups stale dashboards by owner.

When to use it

Use it when business users open dashboards first thing and you want owners to flag stale data before stakeholders ask. A scheduled digest is calmer than real-time alerts when failures are not page-worthy but still matter.

How it works

  1. 1A morning schedule fires before business hours.
  2. 2The flow queries Snowflake for each model's last successful build and joins it to the exposures table to find dashboards backed by stale models.
  3. 3A logic step groups stale dashboards by owner and drops owners with nothing to report.
  4. 4Each owner receives a Gmail digest listing their stale dashboards, the responsible model, and how many hours behind it is.
  5. 5A roll-up count posts to the data team's Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SnowflakeWarehouses, queries, shares.
  2. 2
    Connect GmailRead, draft, send, label.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.