← Blog · October 2026

WordPress Cron Job Not Running? How to Monitor WP-Cron

WP-Cron doesn't run on a real schedule — it runs when someone visits your site. Here's why that matters and what to do about it.

If you've ever noticed that a WordPress scheduled event — a plugin's cleanup task, a scheduled post, an automated backup — stopped running without any error or warning, you've hit one of WordPress's least-understood quirks: WP-Cron.

Unlike a real cron job running on the server, WP-Cron is triggered by HTTP requests to your site. No visitors = no scheduled jobs. Low-traffic sites can miss hours of scheduled work. High-traffic sites can see the same job triggered multiple times simultaneously. Neither is what you want.

How WP-Cron actually works

Every time a page loads on a WordPress site, WordPress checks a list of pending scheduled events. If an event is overdue, it fires it — in the same HTTP request, before the page renders. The code lives in wp-includes/cron.php and is triggered by the wp_loaded action on every front-end and admin request.

This design has some obvious failure modes:

No traffic = no cron. If your site has no visitors for 3 hours, no scheduled events run in that window. A post scheduled for 2am on a low-traffic site may not publish until 8am when the first visitor arrives.
High traffic = duplicate runs. If 50 requests arrive simultaneously and a job is due, all 50 may attempt to spawn the same job. WordPress uses a locking mechanism to prevent this, but it's not bulletproof.
Slow cron blocks page loads. The job runs synchronously in the HTTP request by default. A slow backup task can add 30 seconds to a user's page load time.
Hosting environments break it. Some managed WordPress hosts disable WP-Cron entirely and replace it with a real cron. Others use object caching that interferes with the lock mechanism. Shared hosts sometimes block the loopback request that WP-Cron makes to itself.

The worst part: When WP-Cron stops working, nothing tells you. Plugins that rely on it — email marketing, membership renewals, cache clearing, backups, scheduled posts — silently stop doing their jobs.

Diagnosing WP-Cron problems

Check the scheduled events directly

The easiest way to see what's in your cron queue is the WP Crontrol plugin (free on WordPress.org). It shows all scheduled events, their next run time, and whether they're overdue. An event that's listed as "overdue by 4 hours" on a healthy site indicates a problem.

From the command line with WP-CLI:

wp cron event list

To manually trigger all overdue events:

wp cron event run --due-now

Test whether WP-Cron can reach itself

WP-Cron spawns a loopback HTTP request to yoursite.com/wp-cron.php. If your server can't reach itself (common in some hosting environments, behind certain firewalls, or with misconfigured SSL), scheduled events will queue up indefinitely.

Test the loopback with WP-CLI:

wp eval 'echo wp_remote_get(site_url("wp-cron.php"))["response"]["code"];'

If the response is not 200, you have a loopback problem.

Check if WP-Cron is disabled in wp-config.php

Some performance guides and managed hosting providers recommend adding this to wp-config.php:

define('DISABLE_WP_CRON', true);

This disables the built-in WP-Cron trigger. If it's set and you haven't configured a real server cron to call wp-cron.php, all your scheduled events will stop running permanently — and nothing will warn you.

The recommended fix: replace WP-Cron with a real cron job

For any site that matters, the right fix is to disable WP-Cron's default behavior and replace it with a real server-side cron job:

Step 1: Disable the default WP-Cron trigger

Add this to wp-config.php:

define('DISABLE_WP_CRON', true);

Step 2: Set up a real cron job

Add this to your server's crontab (run crontab -e):

# Run WordPress cron every 5 minutes
*/5 * * * * wget -q -O - https://yoursite.com/wp-cron.php?doing_wp_cron > /dev/null 2>&1

Or with curl:

*/5 * * * * curl -s https://yoursite.com/wp-cron.php?doing_wp_cron > /dev/null 2>&1

Or with WP-CLI (more reliable, handles WordPress-internal locking correctly):

*/5 * * * * cd /path/to/wordpress && wp cron event run --due-now --quiet

On managed hosts like WP Engine, Kinsta, or Flywheel, check their documentation — they typically provide a built-in cron replacement and may require you to use their UI rather than direct crontab access.

Step 3: Verify it's running

After setting up the real cron, confirm it runs every 5 minutes. Create a temporary scheduled event in WordPress and watch with WP Crontrol to verify it fires on time. Or watch cron logs:

grep CRON /var/log/syslog | tail -20

Monitoring: how to know if WP-Cron stops running

Even after the fix, your server cron can silently fail. The /5 * * * * entry in crontab can break if:

The server restarts and crontab isn't persisted (common in containers)
Your hosting migration doesn't carry the crontab over
WP-CLI updates and the path changes
Your site's SSL certificate expires and curl starts failing silently
Disk full prevents the process from spawning

The pattern you want is a dead man's switch: your cron job actively checks in on a schedule, and you get alerted if check-ins stop.

Option 1: Add a heartbeat to your wp-cron.php call

Add a ping to a monitoring service after your WordPress cron runs successfully. For example, with a service like CronWatch:

*/5 * * * * curl -s https://yoursite.com/wp-cron.php?doing_wp_cron > /dev/null 2>&1 \
  && curl -s https://your-monitor.example.com/heartbeat/your-token > /dev/null 2>&1

If the heartbeat stops arriving for more than your grace period, you get alerted immediately — not when a user notices that scheduled posts stopped publishing or a plugin stopped sending emails.

Option 2: Use a WordPress plugin

Plugin	What it does	Cost
WP Crontrol	Inspect + manually run events	Free
Action Scheduler	Reliable async job queue (used by WooCommerce)	Free
WP Cron Status Checker	Alerts when cron hasn't run recently	Free
Cron Job Monitoring (generic)	Dead man's switch monitoring with alerts	Varies

Common WordPress scheduled events that silently fail

These are the scheduled events that site owners most commonly discover have been silently broken for days or weeks:

Scheduled posts not publishing — publish_future_post never fires on low-traffic or misconfigured sites
WooCommerce order cleanup — woocommerce_cleanup_orders leaves failed/pending orders accumulating
Email marketing automations — MailPoet, Mailchimp for WP, FluentCRM all rely on WP-Cron to trigger email sequences
Backup plugins — UpdraftPlus, BackupBuddy, Duplicator scheduled backups never run
Cache clearing — WP Rocket, W3 Total Cache, LiteSpeed Cache fail to purge stale content
Membership renewals — MemberPress, Restrict Content Pro fail to process renewals or send reminder emails
Jetpack stats — site stats stop syncing
Auto-updates — WordPress core, theme, and plugin auto-updates miss their window

Pattern: These failures typically go unnoticed for 2–14 days. The first sign is usually a user report — "My subscription wasn't renewed" or "The scheduled post from last week never published."

Quick checklist: is your WP-Cron healthy?

Install WP Crontrol and check for overdue events
Run wp eval 'echo wp_remote_get(site_url("wp-cron.php"))["response"]["code"];' — expect 200
Confirm DISABLE_WP_CRON status in wp-config.php
If DISABLE_WP_CRON = true, verify the replacement server cron is running
Add a monitoring heartbeat to the cron command so you know when it stops

Get alerted when your cron job stops running

CronWatch is a dead man's switch monitor for cron jobs. Add one line to your cron command, and we alert you if a job is late or stopped checking in — before your users notice something is wrong.

Works with WordPress cron, standard crontab, GitHub Actions, AWS EventBridge, Kubernetes CronJobs, and any scheduled process.

Get early access → Free cron parser

WordPress Cron Job Not Running? How to Monitor WP-Cron

How WP-Cron actually works

Diagnosing WP-Cron problems

Check the scheduled events directly

Test whether WP-Cron can reach itself

Check if WP-Cron is disabled in wp-config.php

The recommended fix: replace WP-Cron with a real cron job

Step 1: Disable the default WP-Cron trigger

Step 2: Set up a real cron job

Step 3: Verify it's running

Monitoring: how to know if WP-Cron stops running

Option 1: Add a heartbeat to your wp-cron.php call

Option 2: Use a WordPress plugin

Common WordPress scheduled events that silently fail

Quick checklist: is your WP-Cron healthy?

Get alerted when your cron job stops running

Related