WordPress uses scheduled tasks for much more than publishing posts. Cron events can trigger plugin maintenance, update checks, email notifications, database cleanup, backups, reports, and queued actions.
When those tasks stop running, the cause is not always obvious. A post might stay in draft mode, a WooCommerce action may remain pending, or booking reminders may arrive late. The most effective fix is to identify where the process is failing before changing settings or deleting events.
What is WordPress Cron?
WordPress has its own scheduling system, known as WP-Cron. On a standard installation, it is triggered when someone visits the site. WordPress then checks whether any scheduled events are due and attempts to run them.
This visitor-based approach is convenient, but it has weaknesses. A low-traffic site may not receive a visit near the scheduled time. On a busy site, frequent visits can trigger overlapping requests. Hosting restrictions, caching, security rules, plugin errors, and failed loopback requests can create additional problems.
Signs that WordPress cron is not working
One delayed task does not necessarily mean the entire scheduler has failed. Look for a pattern such as:
- Scheduled posts remain unpublished after their planned time.
- WordPress or plugin updates do not run as expected.
- WooCommerce orders, stock changes, or emails are delayed.
- Action Scheduler tasks remain pending or show repeated failures.
- Recurring backups, reports, or cleanup jobs stop running.
- A plugin reports missed or overdue scheduled events.
Some plugins use their own queue rather than a basic WordPress cron event. WooCommerce, for example, commonly uses Action Scheduler to manage pending and failed actions. That queue still depends on site or server activity, but it should be inspected separately.
Step 1: Check whether WP-Cron is disabled
Open wp-config.php and search for this setting:
define( 'DISABLE_WP_CRON', true );If it is present, normal WP-Cron has been disabled. That may be deliberate if a real server cron has been configured, but scheduled tasks can stop completely if no replacement is running.
To restore the normal behavior, remove the line or change it to:
define( 'DISABLE_WP_CRON', false );Do not add a second copy of the constant. Take a backup before editing wp-config.php, and be especially careful with punctuation. A small syntax error can make the site unavailable. If editing the file has already caused a PHP or server error, see this guide to solving WordPress fatal errors.
Step 2: Inspect scheduled events
A reputable cron management plugin can show scheduled hooks, recurrence intervals, next run times, and error details. Use one of these tools to find events that are overdue, repeatedly failing, or linked to a plugin recently added or updated.
Avoid deleting unfamiliar events just because their names look technical. Plugins often rely on those hooks, and removing one can interrupt an important process. First identify the plugin responsible and record any error message.
Find the plugin behind a failing hook
After identifying a problematic hook, determine which plugin created it. If possible, test the plugin on a staging site by temporarily deactivating it. If the event begins working afterward, review the plugin’s settings, documentation, logs, and available updates before considering a replacement or rollback.
Step 3: Test loopback requests and Site Health
WP-Cron often requires WordPress to send a request back to its own site. This is called a loopback request. Security rules, HTTP authentication, DNS problems, an HTTP-to-HTTPS mismatch, or a PHP fatal error can block it.
In the WordPress dashboard, open Tools > Site Health and review critical issues. Pay particular attention to loopback requests, REST API errors, scheduled-event warnings, and PHP errors.
Also check the WordPress Address and Site Address under Settings > General. They should use the correct domain and protocol. Problems can appear after a site migration or HTTPS change. For broader hardening guidance, read how to secure WordPress without using plugins.
Step 4: Check for plugin, theme, and PHP errors
A fatal error inside one scheduled task can make the whole cron system appear broken, even when WordPress is still triggering events. Check your hosting control panel’s PHP error log and, where appropriate, the WordPress debug log.
For temporary troubleshooting, add these settings to wp-config.php:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );Reproduce the problem, then inspect wp-content/debug.log. Remove passwords, tokens, email addresses, and other sensitive information before sharing a log with a developer. Turn debugging off when testing is complete, particularly on a production site.
Common causes include an outdated plugin, an incompatible PHP version, exhausted memory, an invalid callback, or custom code that expects data that is not available during a scheduled run. If the problem began after an update, take a backup and check for a newer compatible release before rolling anything back.
Step 5: Review caching, security, and hosting restrictions
Page caching does not usually disable cron by itself, but server caching, bot protection, a web application firewall, or security rules may block the requests that trigger or process scheduled events. Ask your hosting provider whether loopback requests and requests to wp-cron.php are being blocked.
Some hosting plans limit outgoing HTTP requests, PHP execution time, memory, or long-running processes. These limits matter when a backup, import, email queue, or database cleanup task repeatedly times out. Slow site performance can also cause scheduled requests to fail; these WordPress speed troubleshooting steps can help uncover related issues.
Step 6: Consider a real server cron
A server cron can provide more predictable scheduling on low-traffic sites, busy sites, and websites that depend on timely business processes. The usual setup involves:
- Disabling visitor-triggered WP-Cron in
wp-config.php. - Creating a cron task through the hosting control panel or command line.
- Configuring it to request
wp-cron.phpat an appropriate interval. - Checking scheduled events and task queues after the change.
Your host may recommend wget, curl, or a WP-CLI command. The correct method depends on the server, PHP configuration, security rules, and hosting plan, so follow the provider’s documentation instead of copying a command without checking it.
Do not combine frequent visitor-triggered WP-Cron with a server cron unless you understand how both will interact. Duplicate triggers can create unnecessary load and overlapping tasks.
Additional checks for WooCommerce and booking sites
If the site handles orders, appointments, or customer emails, inspect the relevant plugin’s queue as well as WordPress cron. Look for failed actions, long-running tasks, and a backlog that continues to grow.
Once the underlying issue is fixed, process a small group of pending tasks and monitor server resources. Running thousands of queued actions at once can overwhelm shared hosting. For booking websites, also check the plugin’s notification settings and delivery logs, since a cron repair will not correct a separate email configuration problem. This may be useful alongside the Amelia booking configuration guide.
Frequently asked questions
Why are scheduled WordPress posts missing their publication time?
WP-Cron may not have been triggered, may be disabled, or may be failing because of a plugin error, blocked loopback request, or server problem. Start with Site Health and the list of scheduled events.
Should I delete failed cron events?
Usually not. First identify the plugin responsible and fix the cause. Some events are recreated automatically, while others are required for normal site operations.
Is a server cron better than WP-Cron?
It can be more predictable for low-traffic, high-traffic, or business-critical sites, but it must be configured and monitored correctly. The standard WP-Cron system is adequate for many smaller websites.
Can a security plugin break WordPress cron?
Yes. Firewall rules, blocked loopback requests, login protection, and server-level security controls can interfere with scheduled requests. Review security logs and ask your host whether relevant requests were blocked.
Conclusion
To fix WordPress cron jobs, first determine whether the problem comes from disabled WP-Cron, a blocked loopback request, a plugin or PHP error, hosting limits, or a separate task queue. Check logs and scheduled events before deleting anything, test changes carefully, and use a server cron when your site needs more dependable timing. Backups, updates, staging tests, and routine monitoring will make future scheduling problems easier to diagnose.