Key Takeaways (BLUF)
Bottom Line Up Front: WordPress WP-Cron failures are silent by default — if your scheduled backup, WooCommerce order email, or plugin sync job stops running, WordPress does not tell you. The only reliable way to know when critical WP-Cron tasks stop executing is to implement Dead-Man Switch (heartbeat) monitoring: your task pings an external endpoint when it succeeds, and an external service alerts you when the ping stops arriving.
What WordPress Scheduled Tasks Use WP-Cron?
Many critical WordPress operations rely on WP-Cron for scheduling. Here are the most commonly affected:
- Backup plugins (UpdraftPlus, BackWPup, All-in-One WP Migration) — scheduled automatic backups
- WooCommerce — order confirmation emails, subscription renewals, abandoned cart reminders, stock notifications
- Plugins with external sync jobs — Mailchimp sync, CRM data updates, inventory management hooks
- WordPress core — automatic plugin and theme updates, scheduled post publishing, trash emptying
- SEO plugins — sitemap regeneration (Yoast, RankMath), schema update jobs
- Security plugins — malware scanning schedules, login attempt log cleanup
Why WP-Cron Fails Silently
WP-Cron does not have a native failure notification system. When a scheduled task fails to run or executes with an error, WordPress logs nothing visible by default. The task is simply marked as completed (or rescheduled) — even if it threw a fatal error or was never executed.
The root causes of WP-Cron failure fall into three categories:
- Traffic dependency: WP-Cron only fires when a page is requested. On low-traffic sites, "every 24 hours" tasks may actually run every 2–3 days if visitors are sparse
- Task execution errors: A backup script that exceeds the PHP memory limit, a database operation that times out, or a plugin conflict that throws a fatal error — all cause the task to fail without any notification
- WP-Cron being disabled: Sites configured with DISABLE_WP_CRON = true (a common performance optimization) that have not set up a replacement system cron have no scheduled task execution at all
Implementing Dead-Man Switch Monitoring for WordPress Scheduled Tasks
A Dead-Man Switch (heartbeat monitor) works by reversing the notification direction: instead of a monitoring service checking on your task, your task checks in with a monitoring service. If the check-in stops arriving within the expected window, the monitoring service alerts you.
For WordPress WP-Cron tasks, this means adding a heartbeat ping at the end of your scheduled task — after the work is done successfully. If the task fails, the ping is not sent, and WakeMetric alerts you.
<?php
// Example: Monitor a WordPress backup scheduled task with a heartbeat
// Add this to your backup plugin's hook, or functions.php
add_action( 'my_daily_backup_hook', 'run_backup_with_heartbeat' );
function run_backup_with_heartbeat() {
// 1. Run your backup logic
$backup_success = my_backup_function(); // returns true/false
// 2. Only ping WakeMetric if backup succeeded
if ( $backup_success ) {
// Non-blocking HTTP request to WakeMetric heartbeat endpoint
wp_remote_get(
'https://ingest.wakemetrics.com/heartbeat/YOUR-UNIQUE-UUID',
[
'timeout' => 5,
'blocking' => false, // Don't wait for response — fire and forget
]
);
}
// If backup fails: no ping sent.
// WakeMetric detects missing ping and alerts you.
}Replacing WP-Cron With a Real System Cron for Reliability
For critical scheduled tasks, replacing WP-Cron with a real system cron eliminates the traffic dependency problem. Here is how to set it up on cPanel hosting:
- Log in to cPanel → Cron Jobs
- Set the schedule (e.g., every 5 minutes: */5 * * * *)
- Set the command: wget -q -O /dev/null https://yoursite.com/wp-cron.php?doing_wp_cron
- Save the cron job — WordPress scheduled tasks now run on a real timer, not on visitor traffic
- Add DEFINE('DISABLE_WP_CRON', true); to wp-config.php to prevent duplicate WP-Cron executions from page loads
Frequently Asked Questions
How do I know if WP-Cron is currently working on my WordPress site?
Install the WP Crontrol plugin (free, WordPress.org) to see all scheduled tasks, their intervals, and the last time each ran. If you see tasks that were last run days ago when they should run hourly, WP-Cron is not firing reliably. Alternatively, check your backup plugin's logs — most backup plugins record the timestamp of each successful backup run.
My backup plugin says backups are scheduled but I cannot find the backup files. Is WP-Cron the cause?
This is one of the most common WP-Cron failure symptoms. The backup plugin has registered the scheduled task, but the task is failing silently when it executes — often due to a PHP memory limit, a disk space issue, or a file permission problem. Enable your backup plugin's verbose logging, run a manual backup, and check the log for the exact error. Also confirm the backup destination (local folder, Google Drive, S3) is accessible and has sufficient space.
Does WakeMetric monitor WP-Cron tasks?
WakeMetric's free Community Plan monitors your site's external uptime, SSL certificate, and domain expiry. Heartbeat (Dead-Man Switch) monitoring — where your WP-Cron tasks ping WakeMetric to confirm they ran — is available on the WakeMetric Pro plan. The PHP code example above shows how to integrate the heartbeat ping into any WordPress scheduled task.
Conclusion
Silent WP-Cron failures are among the most dangerous WordPress issues precisely because they are invisible until the damage is done — a backup that has not run in three weeks, WooCommerce order emails that stopped going out, or a subscription renewal that failed to process. Heartbeat monitoring closes this visibility gap. And for site-level uptime, the free WakeMetric plugin provides independent external monitoring that catches server failures even when WP-Cron itself is completely stopped.