WordPress Cron Not Working usually means scheduled WordPress events are not being triggered or completed reliably. The safest repair starts by identifying the cron event list, timestamps, Action Scheduler/WP-Cron logs and whether DISABLE_WP_CRON or server cron is configured before changing plugins, code or server settings.
Symptoms
Use the exact symptom and affected URL as the starting point. WordPress Cron Not Working can look similar across sites even when the root cause is completely different.
- Scheduled posts, emails or plugin jobs run late or never run.
- WooCommerce Action Scheduler shows a growing failed/pending queue.
- Site Health reports scheduled-event problems.
- WP-Cron is disabled but no working server cron replaces it.
Common causes
The main areas to investigate are disabled WP-Cron, low traffic, failed loopbacks, stuck jobs, PHP errors, Action Scheduler backlog or incorrect server cron. A good diagnosis narrows these possibilities with logs and request-level evidence instead of changing multiple systems at once.
- DISABLE_WP_CRON is enabled without a functioning system cron.
- Low traffic means pseudo-cron is triggered too infrequently.
- Loopback requests fail.
- A plugin callback crashes or stalls the queue.
- Action Scheduler has a large backlog or database problem.
Safe diagnosis
- List due/overdue events and identify the specific hook that is stuck.
- Check whether WP-Cron is disabled and whether a server cron calls wp-cron.php correctly.
- Review PHP logs and Action Scheduler failures for the same hook.
- Separate one broken job from a global scheduling failure.
Production safety: Create a current backup or recovery point before changing code, database values, plugins, PHP, rewrite rules or server configuration. On WooCommerce and lead-generation sites, test disruptive changes in staging whenever possible.
How the issue is fixed
- Repair the system-cron/WP-Cron trigger path.
- Fix the plugin callback that repeatedly fails.
- Process or clean a backlog carefully after the root cause is corrected.
- Verify new scheduled jobs run at expected intervals.
What to avoid
Avoid this shortcut: Do not delete the entire cron/event queue without understanding which jobs are business-critical. WooCommerce and other plugins can depend on those scheduled actions.
When expert troubleshooting makes sense
If wordpress cron not working is affecting revenue, wp-admin access, publishing, checkout, forms or a live campaign, the priority is a reversible fix with a documented root cause. WP•FIX separates ordinary software faults from security incidents, so suspicious redirects, unknown administrators or injected code are handled through the malware-response path instead of being treated as a normal bug.
FAQ
What usually causes WordPress Cron Not Working?
Common causes include disabled WP-Cron, low traffic, failed loopbacks, stuck jobs, PHP errors, Action Scheduler backlog or incorrect server cron. The visible symptom alone is not enough to identify which one is responsible.
Can WordPress Cron Not Working be fixed without wp-admin?
Often yes. Hosting logs, SFTP/SSH, database tools, browser developer tools or the hosting control panel can provide enough evidence when wp-admin is unavailable.
Should I disable every plugin to fix WordPress Cron Not Working?
A full plugin shutdown can be useful as a controlled test, but on a live business site it can create new failures. It is safer to collect evidence and isolate the likely component with a reversible plan.
When should I request professional WordPress troubleshooting?
If the site is down, checkout or lead generation is affected, the error returns after a temporary workaround, or the cause is unclear from logs, a targeted diagnosis reduces risky trial-and-error.
Need WordPress Cron Not Working fixed?
Send the exact error or broken behavior, the affected URL and what changed before it started. No passwords are requested in the form.
Request professional troubleshooting