Troubleshooting · Troubleshooting
How to Fix Past-Due Actions in the WooCommerce Action Scheduler
Short answer
A past-due action is a pending action whose scheduled time has already passed. A few are normal, because WP-Cron only fires when someone visits the site, but a growing list means the queue runner is not starting. Check WP-Cron and loopback requests first, then drain the backlog with WP-CLI and set up a real server cron.
Key takeaways
- A past-due action is a pending action whose scheduled time has already passed.
- The scheduler tries to run every minute through WP-Cron, in batches of 25 actions.
- A growing past-due list means the runner is not starting, not that the actions are broken.
- WP-CLI runs the queue with a default batch size of 100 until no actions are left.
- Deleting pending actions cancels real work such as renewals and emails.
What is a past-due action in Action Scheduler?
A past-due action is a pending action whose scheduled time has already passed.
Action Scheduler is the background job queue WooCommerce uses for work that should not happen during a page load. Subscription renewals, webhook deliveries, order emails and stock syncs all run as scheduled actions.
A few past-due actions are normal. WP-Cron only fires when someone visits the site, so an action can sit a short while past its time on a quiet store.
A growing list of past-due actions is not normal. It means the queue runner is not starting, and every renewal, email and webhook behind it is late. Open WooCommerce > Status > Scheduled Actions to see the queue.
How does the Action Scheduler queue run?
The queue runs once a minute through WP-Cron, then hands work to the server in batches.
Action Scheduler's own docs say the scheduler attempts to run every minute by attaching to WP-Cron. When it runs, it claims a batch of 25 actions and keeps processing until it uses 90 percent of available memory or has been processing for 30 seconds. See Action Scheduler.
Each action is a hook with a scheduled date and a status. Pending means the job is due and has not been picked up yet.
Complete means it ran. Failed means it ran and hit an error.
The library is built for scale. The same docs say live sites process queues of over 50,000 jobs at a rate of over 10,000 actions per hour. See Action Scheduler.
How do you check whether the queue is stuck?
Open WooCommerce > Status > Scheduled Actions and look at the Pending tab.
| Status | What it means | What to do |
|---|---|---|
| Pending, due date in future | Normal scheduled work | Leave it alone |
| Pending, due date in past | Queue is not running | Check WP-Cron, then drain with WP-CLI |
| Failed | Callback threw an error or timed out | Read the log and fix the hook owner |
| Complete | Action ran fine | Nothing; cleaned up after a month |
| Canceled | Action was called off | Nothing |
Count the past-due rows by hook. If one hook fills the list, that plugin's job is the problem. If every hook is behind, the runner itself never starts.
WooCommerce's system status report shows the Action Scheduler package version and the WP Cron field. That tells you which copy of the library is loaded and whether WP-Cron is on.
What causes past-due actions most often?
The most common cause is WP-Cron turned off with no server cron put in its place.
The queue runner is itself a WP-Cron event. The developer handbook on editing wp-config.php shows the line that turns it off: define( 'DISABLE_WP_CRON', true );.
Other common causes follow in order. A failed loopback request stops the runner from reaching the site.
A firewall or Cloudflare rule can block the server's own address. A fatal error in one callback ends each batch early.
Low traffic also matters. On a quiet store, WP-Cron may not fire for hours, so actions pile up even when nothing is broken. A real server cron fixes that case.
How do you check WP-Cron and loopback requests?
Check Site Health first, because it reports both problems in plain words.
Go to Tools > Site Health > Status. WordPress.org's Site Health guide says loopback requests are used to run scheduled events and by the built-in editors to verify code stability.
If Site Health says your site could not complete a loopback request, the runner cannot call the site itself. Common blocks are basic auth on a staging site, a firewall rule, or a broken certificate.
Search wp-config.php for DISABLE_WP_CRON. If it is true and no server cron exists, you found the cause. Our guide to fixing cURL error 28 covers loopback and request timeouts in detail.
How do you drain the backlog with WP-CLI?
Run the queue from the server to clear the backlog in minutes instead of waiting for WP-Cron.
Action Scheduler's WP-CLI guide says WP-CLI is a much better choice than the default WP-Cron runner for large queues and long-running tasks. Back up the database first, because running the queue sends waiting emails, renewals and webhooks.
wp action-scheduler run --batch-size=100 --batches=0
The same guide says the default batch size is 100, and --batches=0 means batches keep running until no actions are left. See the WP-CLI guide.
To check the queue first, run wp action-scheduler status. The guide says this shows the data store, runner and version in use, plus the number of actions in each status with the oldest and newest dates.
How do you set up a real server cron?
Replace visitor-triggered WP-Cron with a server cron that runs every five minutes.
Add this line above the “That's all, stop editing!” line in wp-config.php:
define( 'DISABLE_WP_CRON', true );
Then add a cron job on the server that runs wp cron event run --due-now every five minutes. Your host panel usually has a cron section, or your host can add the job for you.
The runner still needs loopback requests to work, so fix any loopback failure first. A server cron cannot help if the site cannot reach itself.
On a store with many PHP workers, check how many workers your plan gives you. Our guide to PHP workers in WordPress hosting explains what the number means for background jobs.
How do you fix failed actions?
Read one failed action's log before you touch anything else.
Click a failed action in WooCommerce > Status > Scheduled Actions to see its log. Action Scheduler's docs say all events for each action are logged in the actionscheduler_logs table and shown in the admin screen. See Action Scheduler.
An action running for more than 5 minutes is marked as failed. The same docs say claims sitting for more than 5 minutes are removed before the next batch. See Action Scheduler.
The log message names the error. An API error, a missing order or an expired token points at the plugin that owns the hook. Fix that plugin's settings or update it, then run the failed hook again.
How do you confirm the fix worked?
Reload WooCommerce > Status > Scheduled Actions after five minutes.
Past-due actions should move to Complete on their own, and the newest Pending dates should sit in the future, not the past. The count of past-due rows should fall to near zero.
Run wp action-scheduler status again and compare the numbers. The oldest scheduled date should move forward as the queue drains.
Completed or canceled actions are deleted after more than a month, so the queue cleans itself once it runs. Action Scheduler's docs confirm that housekeeping rule. See Action Scheduler.
What mistakes should you avoid?
The most common mistake is deleting past-due actions to make the count look small.
- Deleting pending actions, which cancels real work such as unsent emails and uncharged renewals.
- Running the queue without a backup, then finding that a flood of late emails went out at once.
- Turning off WP-Cron without adding a server cron to replace it.
- Fixing one failed hook and ignoring the loopback failure that stalls the whole queue.
Use wp action-scheduler clean only for old finished actions. The WP-CLI guide says the clean command defaults to canceled and complete actions, with a --before value of 31 days.
When should you call your host?
Call your host when WP-Cron is on, loopback works, and the queue still does not run.
Ask whether the server blocks loopback requests, whether a firewall rule stops them, and whether PHP workers are full. A queue with no recent starts often points at exhausted workers.
Ask your host to run wp action-scheduler run once from the server if you have no WP-CLI access. That drains the backlog and proves the queue itself is healthy.
If the queue runs by hand but never runs on its own, the server cron is missing or wrong. Our guide to reading the WooCommerce status report shows which fields to send your host.
Update WooCommerce safely first if the loaded library is old. Our guide to updating WooCommerce safely explains the order to update in.
Frequently asked questions
Are a few past-due actions normal?
Yes, a few are normal. WP-Cron only fires when someone visits the site, so an action can sit a short while past its time on a quiet store. A handful of actions a few hours old is fine. Dozens of actions days old, or a count that keeps growing, means the runner is not starting and needs a fix.
Will deleting past-due actions break my store?
Yes, deleting a pending action cancels the work it was meant to do, such as an unsent email or an uncharged renewal. Run the queue with WP-CLI instead so the waiting work completes. Only delete actions you are sure the store no longer needs, and back up the database first.
Do I need WP-CLI to fix past-due actions?
No, but WP-CLI is the fastest way to drain a big backlog. Without it, fix WP-Cron and loopback requests, then let the queue catch up on its own over a few hours. If your host offers WP-CLI, ask support to run the queue once for you.
Why do actions keep going past due on a low-traffic site?
WP-Cron fires only when someone visits the site, so a quiet store may not trigger it for hours. The scheduler tries to run every minute, but it can only run when a visit wakes it up. A server cron that runs every five minutes removes the wait, no matter how little traffic the store gets.
What is the difference between pending and failed actions?
Pending means the action never ran, usually because the runner never started. Failed means the action started and then hit an error or ran past the five-minute limit. Pending actions point at WP-Cron or loopback trouble, while failed actions point at the plugin code behind the hook.
How often should the Action Scheduler queue run?
The scheduler tries to run every minute by design. After a fix, reload WooCommerce > Status > Scheduled Actions after five minutes and look for the pending count to fall. If actions still sit past due after an hour, the runner is still not starting.
Sources
- Action Scheduler - Background Processing Job Queue for WordPress Action Scheduler
- WP CLI Action Scheduler
- Understanding the WooCommerce System Status Report WooCommerce
- Editing wp-config.php WordPress Developer Resources
- Site Health screen WordPress.org Documentation
- woocommerce/action-scheduler GitHub
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
