Zetema
Edit
Data & pipelines · A weekendAnywhere· Source · Sep 2026

Metabase admins can't tell whether an alert was skipped on purpose or broke.

Metabase admins troubleshooting alerts that people expected and never got

Where it stands

  1. Sourced (done)
  2. Kit (done)
  3. Wanted (next)
  4. Building
  5. Solved

How this problem came to be

  1. Found2 sourcesgithub.com/metabase
  2. Quoted3 claimseach checked against its page
  3. BriefWrittenand what solved looks like
  4. MarketNot sizedon the next engine run
  5. Kit5 steps22 tools · 6 routes
  6. People0 want0 live it · 0 would test

The problem, broken down

Who it hurts
Admins of Metabase, an open-source business intelligence tool, when someone asks why their alert never arrived.
The moment
When a user reports a missing alert and the admin sees only ‘Success’ in the history.
What people do today
Admins check Slack, the alert settings or the dashboard behind it, even when nothing is broken.
Why it's unsolved
The status is technically correct, since the alert did run, so it has not been treated as a bug.
What solved looks like
The admin task history shows three distinct states, delivered, skipped because there were no results, and failed, with an automated test for each.

Evidence

Every claim is tied to the source it comes from
Metabase issue #80736: show when an alert was skipped because it was empty ↗
  1. 1Metabase's alert history shows ‘Success’ both when an alert was delivered and when it ran but sent nothing because ‘Don't send if there aren't results’ was on.
  2. 2The issue says this leads admins to investigate Slack, the alert configuration or the underlying dashboard when nothing is actually broken.
  3. 3The issue was opened in August 2026 and is labelled ‘good first issue’.

Written from the cited sources. Anything they don't say is left as a question, not a guess.

Sources

From a public page with a citation.

  1. [1]Metabase docs: alerts
  2. [2]Metabase issue #80736: show when an alert was skipped because it was empty
What the source says, in short

Metabase's alert history shows ‘Success’ both when an alert was delivered and when it ran but sent nothing because ‘Don't send if there aren't results’ was on. The issue says this leads admins to investigate Slack, the alert configuration or the underlying dashboard when nothing is actually broken. The issue was opened in August 2026 and is labelled ‘good first issue’.

Forks 0

Nobody has forked this yet. Be the first.

Market read

How big this is, from the evidence

Not sized yet. The engine reads the figures in the sources, news volume and builders' activity; this fills in on its next run.

For whoever takes this up

The builder's path for this problem

Five steps, each with the tools that fit this problem and a word to carry with you. A starter prompt is ready to paste into any assistant.

Open the path

Discussion 0

No comments yet.