The failure mode
Why nobody catches this today
Your monitoring stack watches things that happen. This failure is a thing that doesn't.
Providers disable endpoints silently. WooCommerce and Shopify auto-drop webhook subscriptions after repeated failures. Secrets rotate, DNS changes, a deploy eats a route, and the sender either retries into the void or simply stops. Uptime monitors can't see it: your endpoint is up; it's the traffic that died. Cron monitors watch jobs you run; nobody watches the deliveries you receive.
The teams that do catch it catch it late: a month-end reconciliation, a customer email, a dashboard that's been flat for a week.
Declare the rhythm
"invoice.paid arrives at least daily." Set it yourself, or let the vault propose it from the history it already holds. A grace window absorbs normal jitter.
The vault keeps score
Every capture feeds the watchdog. While webhooks arrive on cadence, it stays quietly lit; you'll see the green light, not hear from it.
Silence raises the flag
Miss the window and the light goes amber: an alert with the last-seen time, the expected cadence, and the capture history to debug against, because the vault kept everything up to the silence.
Built on the vault, not bolted on
This is why Watchdogs live here and not in a generic monitor: detection needs history. The vault already holds every delivery, so a watchdog switches on with hindsight, knows what "normal" looks like from day one, and hands you the actual requests either side of the gap when you investigate.
Switched on with hindsight
A watchdog runs on the vault's own history: enable one and it already knows what normal looks like, because every capture that came before is on the shelf beneath it. No warm-up period, no blind first week.
- 3 watchdogs on Solo, 20 on Pro, 100 on Team
- Email alerts the moment a window is missed
- At-least-every-N intervals with grace windows
Give every sender a watchdog.
Every capture feeds the alarm that guards it. Free tier, no card.