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

WooCommerce cron issues: diagnose delayed scheduled actions and stuck jobs

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

WooCommerce background work spans WP-Cron, Action Scheduler, payment/webhook retries, email, stock updates, subscriptions, cleanup, and extension jobs. A cron complaint may actually be a failed queue, slow callback, loopback issue, or resource bottleneck.

Inspect Action Scheduler and WP-Cron separately

List pending/failed Action Scheduler actions, hook names, group, age, and error logs. Also list WordPress cron events and overdue hooks. Identify the extension that owns each queue before deleting or rerunning items.

A high pending count with normal throughput may simply reflect a busy batch; age and failure rate add context.

Find the blocking action

Look for repeated failures, long execution, database locks, remote API timeouts, PHP memory/timeouts, or a job creating new jobs faster than workers complete them.

Payment/subscription actions can have real financial effects; do not bulk rerun them without understanding idempotency.

Use a reliable scheduler trigger

On production stores, a system scheduler calling WordPress/Action Scheduler can provide more predictable execution than relying only on visitor traffic. Ensure overlapping invocations are safe and the hosting account has enough PHP/database capacity.

Keep staging from running live WooCommerce schedules against real payment/email endpoints.

Monitor queue age after the fix

Confirm old actions drain, new actions complete on time, failed count stabilizes, and storefront/admin latency remains healthy. Add alerts based on queue age and failures; total queue count alone can be misleading.

  • Separate WP-Cron and Action Scheduler.
  • Identify owning extension.
  • Protect financial job idempotency.
  • Monitor queue age and failures.

Next step

Inspect WP-Cron, Action Scheduler, failed callbacks, locks and resource pressure when WooCommerce background jobs stop keeping up.

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