Skip to content
TutorialOct 2026·8 min read

WooCommerce Action Scheduler: fix past-due, failed and stuck actions

Seeing “past-due actions found”? Find out why WooCommerce’s Action Scheduler fell behind, then clear the backlog with WP-CLI and a server cron.

SmartWP teamThe people who build our plugins
Flat illustration of a queue of task cards piling up under a clock

Level

Intermediate

Steps

5

Time

About 15 minutes

You’ll need

An administrator login, plus SSH with WP-CLI or access to your host’s cron settings

Action Scheduler is the background job queue that comes with WooCommerce. It runs work that shouldn’t keep a shopper waiting, such as webhook deliveries and subscription renewals, at a set time or as soon as it can. Every job is recorded in your database, so you can check what ran and what failed.

When the queue falls behind, your dashboard shows a warning like “Action Scheduler: 12 past-due actions found; something may be wrong.” The logs and Site Health show why, and WP-CLI plus a server cron get the queue moving again.

Where to find scheduled actions in WooCommerce

Go to Tools → Scheduled Actions. With WooCommerce active, the same list also appears under WooCommerce → Status → Scheduled Actions. The Tools page needs an administrator account, while shop managers can use the WooCommerce tab.

The links along the top filter by status. Pending actions are waiting for their time, and Past-due shows the pending ones whose time has already passed. In-progress actions are running now, while Complete, Failed and Canceled ones have finished.

Each row shows the action’s log and its hook. The hook is the job’s name and usually tells you which plugin owns it. Hover over a pending action to Run or Cancel it.

What does “past-due actions found” mean?

A past-due action is a pending job that missed its scheduled time. A few are normal. WP-Cron only starts the queue when the site gets a visit, so a job due at 3:00 might run at 3:02. The Action Scheduler FAQ says to look closer when several past-due actions are more than a day old.

The warning uses the same one-day line. Administrators see it once a pending action is a full day late, so the queue has been stalled or badly behind for at least that long.

Why WooCommerce scheduled actions stop running

WP-Cron isn’t firing

WooCommerce has no cron of its own. Its timed jobs rely on WP-Cron, which runs when someone loads a page, and Action Scheduler asks WP-Cron for a queue run every minute. A quiet store gets few of those visits, and full-page caching that answers visitors without starting WordPress means even a busy store may not trigger it. A DISABLE_WP_CRON line in wp-config.php with no server cron in its place switches WP-Cron off.

Loopback requests are blocked

WP-Cron and Action Scheduler both start their work by sending a request from your site to itself. A firewall rule or the password prompt on a staging site can block that request, and then nothing runs in the background.

The job itself fails

Each failed action’s log says what went wrong. A message ending “no callbacks are registered” means the plugin that scheduled the job has been deactivated or removed. A PHP crash is logged as “unexpected shutdown: PHP Fatal error”, with the file and line. A job still in progress after 5 minutes is marked failed, and its log says it ran that long without completing.

The backlog is too big for the default runner

Each run started by WP-Cron or a dashboard visit works through due actions in small batches and stops after about 30 seconds, so it won’t time out on modest hosting. Only one runs at a time, so after a big import or a long outage the queue is slow to catch up.

How to fix past-due actions in Action Scheduler

The first two steps find the cause. The rest clear the backlog and stop it building up again.

  1. 01

    Read the logs and the oldest date

    In Tools → Scheduled Actions, open Failed and look for hooks that repeat. Then open Past-due and check the oldest scheduled date. The same few hooks failing with one message points to a plugin. Hundreds of mixed past-due actions and no failures points to cron.

    Every admin page you open asks Action Scheduler for a background run, at most once a minute. Refresh this screen after a minute or two. If the past-due count drops, the queue works but nothing triggers it while you’re away, which is how a store can look fine by day and fall behind overnight.

  2. 02

    Check that WP-Cron and loopbacks work

    Open Tools → Site Health. “A scheduled event is late” or “Your site could not complete a loopback request” means the trigger is the problem. With SSH access, WP-CLI can test the WP-Cron trigger that WooCommerce’s scheduled jobs depend on:

    WP-CLI
    wp cron test

    “Success: WP-Cron spawning is working as expected” means the trigger works. An error names what’s in the way, such as DISABLE_WP_CRON or the HTTP status the loopback returned. Ask your host to allow requests from the site to itself, or go on to step 4.

  3. 03

    Run the backlog with WP-CLI

    WP-CLI runs the queue directly on the server, without a web request’s time limit. Check the counts first, then run it.

    WP-CLI
    # How many actions are in each status, with the oldest and newest
    wp action-scheduler status
    
    # Run due actions in batches of 100 until none are left
    wp action-scheduler run

    Add --batches=1 to try a single batch first. The Action Scheduler WP-CLI reference has options to run one hook or group at a time.

  4. 04

    Run WP-Cron from the server

    A server cron fires on time whether anyone visits or not. Add one first, then turn off the visitor-triggered WP-Cron. Action Scheduler wants a run every minute, so schedule it that often.

    Crontab
    * * * * * cd /path/to/your/site && wp cron event run --due-now --quiet
    wp-config.php
    define( 'DISABLE_WP_CRON', true );

    Replace the path with your site’s folder. If nothing runs, use the full path to wp (which wp prints it), because cron doesn’t load your shell’s PATH. Without WP-CLI, a cron that requests https://yourstore.com/wp-cron.php does the same job, as the WordPress plugin handbook shows. On managed hosting, ask your host first: some already run WP-Cron from the server.

  5. 05

    Deal with the failed actions

    Fix the cause the log names. Reactivate the plugin behind a “no callbacks” error if you still need its jobs, and send a PHP error’s file and line to that plugin’s developer.

    Run and Cancel only appear on pending actions, so the Scheduled Actions screen can’t rerun a failed one. It stays as a record until you remove it with the Delete bulk action or a clean-up deletes it. A recurring job still schedules its next run, unless its log says “This action appears to be consistently failing.” Then it has stopped repeating, so check that a new pending copy appears once the cause is fixed.

A stack of old task cards being trimmed into a bin
Old completed and failed actions can go; pending ones should stay.

How to clear old scheduled actions in WooCommerce

Action Scheduler cleans up after itself. Completed and canceled actions are deleted once they’re 31 days old, logs included. You only need to step in when the tables grow faster than that, usually because a plugin schedules far more jobs than it needs, or because the queue stalled and the clean-up only runs when the queue does.

Use WP-CLI for it. The clean command deletes in batches and removes each action’s log entries too, which a DELETE query in phpMyAdmin leaves behind.

WP-CLI
# Completed and canceled actions older than a week
wp action-scheduler clean --status=complete,canceled --before='7 days ago'

# Failed actions, once you've read their logs
wp action-scheduler clean --status=failed --before='30 days ago'

What Action Scheduler 4.0 changed for failed actions

Before version 4.0, Action Scheduler kept failed actions forever by default. Action Scheduler 4.0.0 came with WooCommerce 11.0 and deletes them once they’re three months old, a window its developers chose to match a quarterly accounting cycle. The clean-up also moved to its own daily task at 3 am site time.

Run wp action-scheduler version to see which version your store uses. If you need failed actions for longer, say for an audit or a payment dispute, change the period with a filter in a code snippets plugin or your child theme:

PHP
// Keep failed scheduled actions for six months instead of three.
add_filter( 'action_scheduler_retention_period_for_failed', function () {
	return 6 * MONTH_IN_SECONDS;
} );

Returning false from the action_scheduler_enable_failed_action_cleanup filter turns the purge off.

A dashboard panel with rows of status dots
One screen for what's due, what's late and what failed.

Watch the WooCommerce Action Scheduler from one screen

When you only want to know whether the queue is keeping up, a summary is quicker to read than the full list. Admin Powerups adds a scheduled action monitor for WooCommerce: switch on Scheduled action monitor in the Developer group under WooCommerce → Powerups, then click Configure and open the Monitor tab.

Its Queue health panel counts overdue, failed and running actions, and flags any that have run for over 5 minutes, which usually means stuck. It shows which hooks fail most and how big the tables are, and warns you when actions run late.

From the Overdue list you can run an action now, and from Failed you can retry one, which adds a fresh copy to the queue. Cancel, delete and Purge old actions each ask you to type a word to confirm. Action Scheduler’s own actions and WooCommerce database updates are Protected and can’t be changed. Jobs that handle payments, renewals or webhooks carry the label “May charge, refund or send again.”

If wp action-scheduler version still shows 3.x, set Keep failed actions for (days) above 0 and the power-up deletes older failed actions once a day, much as 4.0 does. On Action Scheduler 4, leaving it at 0 keeps the three-month default. The Scheduled action monitor docs cover every option, and the Cron inspector power-up lists every WP-Cron event when cron itself is the trouble.

Both are admin-only tools that stay off until you switch them on. With every power-up on, Admin Powerups adds 0 queries to your storefront.

If the past-due warning keeps coming back, download Admin Powerups and keep the monitor on. Planning an update? Our guide to updating WooCommerce safely covers what to check before you move to 11.x, and the launch-day checklist is worth a run-through before your next big sale.

Keep reading