A cronjob that fails silently is often noticed days later – when orders are stuck, backups are missing or newsletters never go out. Cronjob.de calls your address on schedule and tells you as soon as something goes wrong: by email, in Slack, Teams or Discord, or via webhook.
The problem
The cron on a Linux server at most emails the output of a command – it never learns whether a page it called answered with an error. Hosting providers' cron managers usually report nothing at all. And a cron that piggybacks on page visits, like WP-Cron, simply stops when nobody comes by.
How it works
You learn when a cronjob switches from running to failing – and get an all-clear as soon as it recovers. No flood of emails for per-minute jobs.
Your server answers with an error code (4xx, 5xx) or refuses the connection. Returning status 500 from your script reports your own errors too.
At most one message every 15 minutes with several affected cronjobs combined – or at most one message per day.
By email and additionally in Slack, Microsoft Teams or Discord. Or as a signed JSON webhook to an address of your choice, for example for Pushover or Telegram.
The last 20 calls per cronjob with status, runtime and up to 5,000 characters of the response. Plus statistics for the last 200 runs.
When calling your address we see how long its SSL certificate is valid, and on request we let you know in good time.
Tip
Many scripts abort and still answer with status 200 – from the outside everything looks fine. Catch errors and return status 500. Cronjob.de then reports exactly that run, and the error message shows up in the log.
<?php
try {
// ... die eigentliche Arbeit ...
echo 'OK';
} catch (Throwable $e) {
http_response_code(500);
echo 'Fehler: ' . $e->getMessage();
}
FAQ
Every sign-up starts with 14 days of Unlimited – with failure notifications, log and one-minute intervals. After that, up to five cronjobs keep running for free.
Start for free See pricing