Merchlint
Available now
Next, in this order
  • DeutschDE
  • EspañolES
  • FrançaisFR
  • ItalianoIT
  • PortuguêsPT
  • NederlandsNL
  • SvenskaSV
  • TürkçeTR

A language shows up here once its pages are actually written. Nothing on this site is machine-translated, except a few German and Spanish pages that no native speaker has reviewed yet.

Install free Install
← All checks

Scheduled actions stopped running

When the background queue stalls, sales never end, emails never send and stock never syncs—while the storefront looks perfectly healthy.

Group
Environment
Confidence
F — fact read directly from your store
Name on the plugin screen
Scheduled jobs are not running
Included in
the free plugin
Updated
Code
E4

The symptom

Nothing looks broken. Pages load, orders come in, the admin is responsive. But a scheduled sale that should have ended last month is still running, a follow-up email never arrived, and an integration that syncs stock every hour last synced in July.

In WooCommerce → Status → Scheduled Actions there is a Past-due tab, and it has entries in it. Sometimes thousands.

Often the first sign is a notice at the top of the admin, in exactly these words:

Action Scheduler: 848 past-due actions found; something may be wrong. Read documentation »

Only the number changes (with a single action it reads 1 past-due action found). By default WooCommerce shows the notice once at least one action is more than a day overdue.

What it costs

WordPress has no real scheduler. It has WP-Cron, which only runs when somebody visits the site, and WooCommerce layers Action Scheduler on top of it for anything that must survive a restart. Almost everything that happens later in a store rides on that queue:

  • Scheduled sales start and end late. Since WooCommerce 10.5 every sale with a date gets its own actions in the woocommerce-sales group, wc_product_start_scheduled_sale and wc_product_end_scheduled_sale, timed to the minute. The daily woocommerce_scheduled_sales event, which used to do all of it once a day, now only catches what they missed. Both run on this queue. Until they do, a simple product on WooCommerce older than 11.1 shows and charges the old price: a sale that should have ended keeps selling cheaper, and a sale that should have started still charges the regular price. This is the direct cause behind a sale that will not stop. From 11.1 the product page and the cart work out the right price on their own. Variations take their price from the sale dates on every version, but the variable product page can still show the old one. On every version the stored price, the price filter, sorting by price and “on sale” product lists wait for the action.
  • Emails do not go out. Order follow-ups, abandoned cart reminders, review requests, renewal notices—all queued.
  • Stock and price syncs stall. ERP, marketplace and feed integrations queue their work; the catalog silently drifts from reality.
  • Subscription renewals do not charge. On stores that sell subscriptions this is revenue that simply never bills.

The reason this survives for months is that it produces no error anywhere a human looks. There is no white screen. There is just a store that quietly stops doing anything it was told to do later.

How to check it yourself

Three angles, from cheapest to most complete.

1. The screen WooCommerce already gives you. Go to WooCommerce → Status → Scheduled Actions and open the Past-due tab. A handful of items a few minutes old is normal. Anything more than a day old is not: on a store with any traffic the queue clears several times a day.

2. From WP-CLI:

wp cron event list --fields=hook,next_run_gmt,next_run_relative --format=table
wp action-scheduler status

wp cron event list shows now for every event whose time has already passed; the next_run_gmt column shows when that was. If most events say now and their times are hours or days ago, WP-Cron itself is not firing.

3. Check whether WP-Cron was switched off and never replaced. In wp-config.php:

grep -n "DISABLE_WP_CRON" wp-config.php

define( 'DISABLE_WP_CRON', true ); is not a bug by itself—it is the recommended setup on busy stores. It becomes a bug when nobody ever added the real system cron that was supposed to replace it. Confirm the replacement exists:

crontab -l | grep wp-cron

Before a planned sale, Black Friday for example. Set the sale dates a few days ahead, then open WooCommerce → Status → Scheduled Actions, the Pending tab, and search for wc_product_start_scheduled_sale. Every product you set up should have an action there with the start you chose; a sale with an end date also has wc_product_end_scheduled_sale. A sale set in the product editor starts at midnight of the chosen day and ends at 23:59:59, store time. Then open the Past-due tab. If it holds hundreds of actions, or any that are hours old, the queue is not keeping up, and on Black Friday your sale actions will wait in the same line—fix the queue first, as below.

This applies from WooCommerce 10.5. Older versions have no actions per product, only the daily event. A sale whose dates were set before the store moved to 10.5 may also have no action of its own; the daily event covers it, once a day.

How to fix it

  1. Give the site a real scheduler. Either through your host’s cron panel, or a crontab entry every five minutes:

    */5 * * * * curl -s https://example.com/wp-cron.php?doing_wp_cron >/dev/null 2>&1

    Then set DISABLE_WP_CRON to true, so visitor requests stop trying to run the queue as well.

  2. Drain the backlog once, so you are not waiting for it to catch up on its own:

    wp action-scheduler run --batch-size=50
  3. Deal with what the backlog was hiding. Overdue sale actions run when the queue restarts, so the prices go back to what you set. What does not go back are the orders placed in the meantime: for simple products on WooCommerce older than 11.1 they were charged the price that should no longer, or not yet, have applied. Queued emails can go out late too, long after the order they belong to. Check prices and the orders from the gap before you assume the catch-up did the work.

  4. Look at failed actions too, not only pending ones. A job that fails every run keeps the queue busy without ever completing.

When it’s a false alarm

  • A brand-new store with nothing scheduled yet gets no finding, because nothing is overdue. That does not prove the queue works, either.
  • Your host runs cron from outside the site, which WordPress cannot see. With DISABLE_WP_CRON set, Merchlint looks for a sign that something still runs the queue: an action that completed or failed within the last day. If there is one, and nothing is overdue, there is no finding.
  • A deliberately paused queue during a migration or a bulk import. Legitimate, and worth un-pausing before you forget.

How Merchlint finds it

Merchlint looks at two queues separately: WP-Cron’s own list of scheduled events, and Action Scheduler’s actionscheduler_actions table (with your table prefix in front, such as wp_actionscheduler_actions). In each it counts the pending actions whose time has passed, and it reports the queue when the oldest one is more than a day late. Below a day, a broken store and a quiet one look the same. The finding shows how many actions are overdue, how late the oldest one is, and its hook name, which usually tells you what stopped working.

A second finding covers a switched-off WP-Cron: DISABLE_WP_CRON is set and no action has completed or failed in the last day. Together they tell “cron is off” apart from “cron is on but drowning”.

Confidence: F—fact from the database. A scheduled time is either in the past or it is not.

This check moved into the free version on August 20, 2026, because it names the cause behind a whole class of other findings—including sales that will not end and stock that never updates. A report that lists the symptoms without naming that cause sends you fixing products one at a time.

Run this check on your store

Doesn't match what you see in your store? Email us—we read every message. contact@merchlint.com