Didn't Run
Backup plugins email you when a backup runs. None of them email you when one doesn't. Didn't Run watches every scheduled job across every site you manage, and tells you the moment one goes quiet.
Join the waitlistNot built yet. This page exists to find out whether the problem is worth solving. No payment, no date, no commitment either way.
UpdraftPlus, BackWPup, WPvivid — each generates a report when a backup runs. No run, no report, no signal. Silence reads identically to success.
A quiet client site can miss its 2am window for days. UpdraftPlus's own documentation lists the causes — no visitors, disabled schedulers, broken loopback connections, misconfigured external cron — and notes that scheduler problems "can affect any scheduled backup plugin."
"Email me only on warnings and errors" is a paid feature. Turn it on and your inbox goes quiet — which now means both "everything is fine" and "nothing has run since September."
We do not run your jobs. We watch them. Your scheduler stays yours, so there is nothing new that can break.
$29 / month · a guess, not an offer
For comparison: a general site-monitoring suite runs about €1.99 per site per month and covers uptime, SSL, PHP errors and vulnerabilities. None of them watch scheduled jobs. This fills that gap — it doesn't replace them.
There is no product here. I looked into this because backup plugins report when a backup runs and never when one doesn't, and I wanted to know whether that actually costs anyone anything.
Several people have since told me they catch it another way: a real server cron, an Uptime Kuma push monitor, or watching the remote backup destination for a file that should have arrived. Those are good answers and they may be the whole answer.
So I am asking before building. If a scheduled job has silently stopped on a site you manage, I would like to hear what happened and how you found out.
Yes, and it still matters. A real cron fixes triggering. It does not tell you when a job starts and then dies halfway.
Checks run on infrastructure independent of both your sites and our own dashboard, so an outage on our web front end does not stop monitoring or alerting. If we cannot reach your site, you are told that too — a monitor that goes quiet is worse than no monitor at all. Alert delivery is redundant across email and webhook, and incident history is visible in your account.
Anything registered in WP-Cron, which is nearly everything. We read the schedule — we don't integrate per-plugin.
The plugin is GPL, as WordPress.org requires. The monitoring service is ours.
That is the registered company behind Didn't Run. Payments are handled by Stripe and settle to Mailotte LTD — same business, legal name on the card statement.
Didn't Run is operated by Mailotte Ltd, a company registered in England and Wales (No. 17119010). Billing is handled by Stripe and your payment appears on your statement as MAILOTTE LTD. Support reaches a monitored address and is answered within one business day — help@didntrun.com.
There is no date, because there is nothing being built. If enough people tell me this costs them real time or money, that changes. If they tell me a server cron and a destination check already cover it, that is a good answer and I will say so here.
The plugin reports job names and completion times. It does not read post content, customer records or database contents, and it never needs admin credentials. Data is held in the UK and deleted within 30 days of cancellation.