Monitoring WordPress cron: is WP-Cron really running?

Setup

Set up in three steps

1. Create a heartbeat

   In your account, create a new one under “Heartbeats”, hourly, with one hour of leeway. You receive a ping address of its own, such as https://runcheck.de/a8k3m2x9q1.

2. Without code: install the plugin and enter the address

   In the WordPress admin, search for “Cronjob.de” under “Plugins”, then install and activate Cronjob.de – Reliable Cron. Under “Tools › Cronjob.de”, enter the ping address in the field “Heartbeat (optional)” and save. From now on every WP-Cron run checks in, at most every 5 minutes.

3. Or: a must-use plugin with a few lines

   If you prefer not to install a plugin, upload the file wp-content/mu-plugins/cronjob-heartbeat.php via FTP. The mu-plugins folder does not always exist; if not, create it. WordPress only loads PHP files directly in this folder, not in subfolders. Must-use plugins are always active. This file schedules an hourly WP-Cron task that checks in with Cronjob.de.

   <?php
   // wp-content/mu-plugins/cronjob-heartbeat.php
   // Checks in with Cronjob.de every hour via WP-Cron. If the check-in is missing, WP-Cron is not running.
   add_action( 'cronjob_de_heartbeat', function () {
       wp_remote_get( 'https://runcheck.de/a8k3m2x9q1', array( 'timeout' => 5 ) );
   } );
   add_action( 'init', function () {
       if ( ! wp_next_scheduled( 'cronjob_de_heartbeat' ) ) {
           wp_schedule_event( time(), 'hourly', 'cronjob_de_heartbeat' );
       }
   } );

4. Trigger it once and check

   Open https://your-domain.com/wp-cron.php once in your browser; with the next WP-Cron run at the latest, the first check-in arrives, and “Waiting for the first check-in …” turns green in your account. With the must-use plugin and WP-CLI you can trigger it directly:

   wp cron event run cronjob_de_heartbeat

The ready-made lines for Linux, PHP, Python, Node.js, n8n, Make, Supabase and Vercel are on the page Cron job monitoring. Your own ping address appears in your account once you create the heartbeat, with the same lines ready to copy.

When something fails

What happens when a run fails

If the check-in is missing, WP-Cron is not running: because no visitors came, a cache sits in front, a plugin blocks it or the site is down. After the leeway you get a message, and an all-clear as soon as WP-Cron runs again. That way you also know scheduled posts and shop tasks are no longer piling up.

FAQ

Common questions about WordPress-Cron

How do I check whether WP-Cron is running?

By hand under “Tools › Site Health”: WordPress lists late or failed scheduled events there. To be told automatically, use a heartbeat as above, because it contacts you as soon as the signs of life stop.

Is the cronjob that calls wp-cron.php not enough?

It makes sure WP-Cron gets triggered, and from the Plus plan we report by email when the call ends with an error. The heartbeat additionally tells you that WP-Cron really processes the scheduled tasks. The plugin “Cronjob.de – Reliable Cron” sets up both.

How do I monitor WP-Cron when I run it with WP-CLI on my own server?

Append the check-in to the crontab line; WP-CLI's exit code goes along: */5 * * * * cd /var/www/html && wp cron event run --due-now --quiet; curl -fsS -m 10 --retry 3 https://runcheck.de/a8k3m2x9q1/$? > /dev/null. You then need no plugin.

Does this monitor WooCommerce tasks too?

Indirectly. WooCommerce handles a lot through the Action Scheduler, which runs on WP-Cron by default. The heartbeat shows that WP-Cron runs; whether each single task inside succeeds, you see under “WooCommerce › Status › Scheduled Actions”.