Developer · Explainer
What Is Action Scheduler in WordPress? Background Tasks Explained

Short answer
Action Scheduler is a background job queue for WordPress, built by the WooCommerce team and bundled with WooCommerce and many other plugins. It stores tasks such as sending emails, syncing data or renewing subscriptions in its own database tables and runs them in small batches, triggered mainly by WP-Cron. You can view its queue under Tools > Scheduled Actions.
Key takeaways
- Action Scheduler queues and runs background tasks for plugins.
- It ships with WooCommerce and many other popular plugins.
- Actions are stored in custom database tables, not as WP-Cron events.
- View and manage the queue under Tools > Scheduled Actions.
- Past-due actions usually mean WP-Cron or the queue runner is not running.
What is Action Scheduler?
Action Scheduler is a library that lets WordPress plugins queue tasks to run later or repeatedly in the background, with a log of every run, so heavy work does not slow down page loads.
It was created for WooCommerce Subscriptions and is now maintained by the WooCommerce team.
The official Action Scheduler website describes it as a scalable, traceable job queue for background processing.
It is not a plugin you usually install yourself. Plugins include it, and WordPress loads the newest bundled copy.
Because several plugins can bundle different versions, WordPress loads only the newest copy found. That keeps every plugin on the same, most recent code.
What does Action Scheduler do?
It stores scheduled tasks, called actions, runs them when they are due, records whether they succeeded or failed, and retries or logs errors for you to review.
Typical actions include sending queued emails, processing subscription renewals, syncing products with marketplaces, generating reports and cleaning old data.
Each action has a hook name, arguments, a scheduled time and a status.
Actions can be one-off, recurring at a fixed interval, or follow a cron-style schedule such as every Monday at 9am.
| Status | Meaning |
|---|---|
| Pending | Waiting to run |
| In-progress | Running now |
| Complete | Finished successfully |
| Failed | Ran but hit an error |
| Canceled | Stopped before running |
Which plugins use Action Scheduler?
WooCommerce and its extensions use it heavily, and many marketing, email, backup and integration plugins bundle it for their own background jobs.
If you run WooCommerce, Action Scheduler is already on your site.
The WooCommerce plugin page lists the plugin, which includes Action Scheduler among its components.
Seeing many different hook names in the queue is normal on sites with several plugins.
Hook names usually start with a plugin prefix, which makes it easy to tell which plugin created an action.
How is it different from WP-Cron?
WP-Cron stores scheduled events in a single option and runs them on page loads, while Action Scheduler stores each action in its own tables, processes them in batches and keeps a detailed log.
Action Scheduler still relies on WP-Cron to start its queue runner, which usually checks for due actions every minute.
It can also start processing through background requests when the admin area is in use, which helps on sites with little traffic.
The WordPress cron documentation explains how WP-Cron works and its limits.
Our guide on scheduling events with wp_schedule_event covers the core WP-Cron functions developers use.
Where can you see scheduled actions?
Go to Tools > Scheduled Actions in the dashboard, or WooCommerce > Status > Scheduled Actions on WooCommerce sites, to search, filter and inspect actions and their logs.
Filter by status to see pending or failed actions quickly.
Each action's log shows when it was created, started and finished, plus any error messages.
You can run a pending action manually or cancel it from this screen.
Be careful when cancelling. A canceled subscription renewal or sync will not run, which can leave data out of date.
What are past-due actions?
Past-due actions are pending tasks whose scheduled time has passed without running, which usually means WP-Cron is not firing, the queue is overloaded or actions keep failing.
WooCommerce may show a notice about past-due actions in the dashboard.
Our guide on fixing past-due Action Scheduler actions walks through the causes and fixes.
Often the root cause is WP-Cron. Our guide on fixing WP-Cron not running covers that side.
How do you make Action Scheduler more reliable?
Run WP-Cron from a real server cron job, keep the queue healthy by fixing failing actions, and make sure your hosting has enough PHP workers for background processing.
Our guide on disabling WP-Cron and using a real cron job shows the server-side setup.
On busy stores, WP-CLI can process the queue directly with its own command, which avoids web request time limits.
The Action Scheduler WP-CLI documentation lists the run command and its options.
Does Action Scheduler slow down a site?
Normally no, because it runs in small batches in the background, but a very large or failing queue can add database load and slow the admin area.
Large numbers of completed actions make the tables bigger. Action Scheduler deletes old completed actions automatically after a retention period.
If the admin area is slow on a store, check the queue size. Our guide on the slow WooCommerce orders page covers related performance issues.
Object caching and a well-tuned database also help sites with heavy background work.
Can you delete Action Scheduler tables?
Do not delete its tables or the library while plugins depend on it; to clean up, remove completed or canceled actions through the Scheduled Actions screen or let automatic clean-up run.
Deleting tables by hand can break WooCommerce and other plugins.
If the tables are very large, ask your host or developer to check them before any manual clean-up, and test on a staging copy first.
If you uninstall every plugin that used it, the tables may remain. They are safe to remove only after a backup and when nothing uses them.
How do developers use Action Scheduler?
Developers call functions to schedule single, recurring or cron-style actions, or to run an action as soon as possible in the background, then hook their own function to the action name.
The library is open source. The Action Scheduler repository on GitHub contains the code and issue tracker.
Groups let developers tag related actions, which makes them easier to find and cancel together.
Batch size and time limits can be tuned with filters, which helps on hosting with strict PHP time limits.
Keep each action small and idempotent, so retries do not cause duplicate emails or orders.
What should site owners check regularly?
Look at Tools > Scheduled Actions now and then for growing numbers of pending or failed actions, read failure messages, and fix the plugin or setting behind them.
A healthy queue shows mostly completed actions and few pending ones.
What should you do with failed actions?
Read the log message, fix the cause, such as an expired API key or a missing product, then let the plugin reschedule or run the action again.
If a failed action belongs to a plugin you removed, it can usually be deleted safely.
Repeated failures from one hook usually point to one plugin. Update or reconfigure it.
Add a check of scheduled actions to your monthly maintenance routine.
Note the number of pending actions each month. A steady rise is an early warning that something needs attention.
Frequently asked questions
What is Action Scheduler in WordPress?
It is a background job queue used by WooCommerce and many plugins to run tasks such as emails, renewals and syncs later or on a schedule, with a log of each run.
Where do I find scheduled actions in WordPress?
Go to Tools, then Scheduled Actions. On WooCommerce sites the same list is also under WooCommerce, then Status, then Scheduled Actions, with filters for each status.
Is Action Scheduler a plugin?
It is a library bundled inside plugins such as WooCommerce. You normally do not install it separately; plugins load it for you.
Why are my scheduled actions past due?
Usually because WP-Cron is not running, the queue is overloaded, or actions keep failing. Check WP-Cron and read the failure logs.
Can I delete Action Scheduler tables?
Not while plugins use them. Clean up completed actions instead. Remove the tables only after a backup when no plugin depends on them.
Sources
- Action Scheduler actionscheduler.org
- WP-CLI Action Scheduler Docs
- Cron WordPress Plugin Handbook
- woocommerce/action-scheduler GitHub
- WooCommerce WordPress.org Plugins
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.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


