Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

WordPress

WordPress cron troubleshooting: why scheduled events run late or not at all

Published August 2026 · 2 min read · Updated 2026-09-05

WordPress cron is request-triggered scheduling by default, not a traditional always-running system scheduler. Missed or delayed events can result from low traffic, disabled wp-cron, loopback/request failures, long-running callbacks, queue backlogs, or plugins that schedule more work than the hosting account can process.

Inspect scheduled events and lateness

Use WP-CLI or a trusted cron inspection tool to list hooks, next-run timestamps, recurrence, and overdue events. Identify which plugin owns a hook before deleting anything.

A large repeated queue may come from one failing callback; the scheduler itself can still be healthy.

Check how cron is triggered

If DISABLE_WP_CRON is set, confirm a real system cron or platform scheduler calls wp-cron or WP-CLI on the intended interval. If default request-triggered cron is used, low-traffic sites may naturally run tasks late.

Loopback restrictions, DNS, TLS, or authentication can prevent self-requests.

Find long or failing jobs

Review PHP errors, plugin logs, database locks, external API failures, memory/timeouts, and execution duration for the specific hook. Long jobs can overlap if the plugin lacks proper locking.

WooCommerce Action Scheduler is a separate queue worth inspecting when WooCommerce extensions are involved.

Move to controlled scheduling when needed

For predictable production scheduling, disable request-triggered cron only after a system scheduler is proven. Run jobs frequently enough for the application but avoid triggering overlapping copies.

  • List overdue hooks.
  • Verify the trigger mechanism.
  • Trace the owning plugin/job.
  • Prevent overlapping long runs.

Next step

Inspect WP-Cron events, trigger method, loopback requests and failing callbacks so delayed jobs are traced to the scheduler, plugin or hosting layer involved.

Explore DotMoose WordPress hosting

Keep reading

Related guides.

Do I need web hosting for WordPress? What WordPress actually needs

Self-hosted WordPress needs web hosting, but it does not require a specially branded WordPress plan. Compare WordPress.com, regular shared hosting, WordPress hosting and VPS options.

Read the guide

How to move web hosting without downtime

Move a website and database with destination testing, final synchronization, controlled DNS cutover, and rollback while preserving separate mail routing.

Read the guide

PHP timeout troubleshooting: PHP, PHP-FPM or the web server?

Find which PHP timeout fired, check the right configuration, and distinguish PHP execution limits, PHP-FPM termination and nginx FastCGI read timeouts.

Read the guide

More wordpress guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move