WP-Cron is fine for light site housekeeping, but Action Scheduler is the better choice for serious, queued, high-volume WordPress tasks. WordPress starts scheduled events during normal page loads, not from a true system clock, which explains why low-traffic sites can miss timing targets [source: WordPress Developer Resources].
TLDR: WP-Cron works well for simple jobs such as checking updates, publishing scheduled posts, or clearing small caches. Action Scheduler is built for heavier work, such as sending order emails, renewing subscriptions, syncing stock, or processing background batches. For example, a WooCommerce store handling 500 orders per day may see email or stock sync delays if WP-Cron waits for traffic, while Action Scheduler can process tasks in smaller tracked batches. The practical rule is simple: use WP-Cron for basic timing, use Action Scheduler for reliable queues.
What WP-Cron Actually Does
WP-Cron is WordPress’s built-in scheduling system. It checks for due tasks when someone visits the site. If a task is ready, WordPress tries to run it during that request or shortly after it.
This is simple and convenient. No server setup is required. Plugin developers can schedule events with familiar functions such as wp_schedule_event() and wp_next_scheduled().
Common WP-Cron jobs include:
- Publishing scheduled posts
- Checking for WordPress core, theme, and plugin updates
- Sending basic plugin emails
- Clearing expired transients
- Running small cleanup tasks
The catch is that WP-Cron depends on visits. A busy site may run tasks often. A quiet site may not. A staging site with no traffic may sit there doing nothing, which drives developers mad when a “scheduled” job runs 27 minutes late for no obvious reason.
Where WP-Cron Starts to Struggle
WP-Cron is not a real server cron job. It is a simulated scheduler. That design is useful for shared hosting, but it creates limits.
The biggest problems are:
- Traffic dependency: no visits can mean no task execution.
- Request limits: long jobs may hit PHP timeouts.
- Poor visibility: failed or stuck events are not always easy to inspect.
- Duplicate pressure: bad plugin code can schedule too many events.
- Timing drift: “run at 10:00” may become “run sometime after 10:00.”
For a blog, this is usually acceptable. For a store, membership site, learning platform, or booking system, it can become a problem fast. A delayed renewal email is annoying. A delayed payment capture or inventory sync can cost money.
What Action Scheduler Does Differently
Action Scheduler is a background processing library used by WooCommerce and many extensions. It stores tasks as actions, tracks their status, and processes them in batches. Each action can be pending, running, complete, failed, or canceled.
That tracking is the big advantage. Site teams can see what happened. They can retry failed items. They can inspect error logs. They can process large sets of work without trying to cram everything into one page load.
Action Scheduler is designed for jobs such as:
- Processing WooCommerce order webhooks
- Sending transactional emails
- Running subscription renewals
- Syncing products with an external system
- Importing or exporting data in batches
- Running CRM, ERP, or fulfillment updates
According to the project site, Action Scheduler is used by WooCommerce and can process large queues of background jobs [source: Action Scheduler]. That makes it a better fit when tasks matter and failure needs to be visible.
WP-Cron vs Action Scheduler: The Practical Difference
WP-Cron answers the question: “When should this event be attempted?”
Action Scheduler answers a better question for serious workloads: “What exact task must run, what is its status, and what happens if it fails?”
That difference sounds small until a site has 8,000 subscribers, 40 plugins, and a nightly sync with a shipping provider. Honestly, it feels like WP-Cron was made for polite chores, while Action Scheduler was made for the ugly queue of real business work.
| Feature | WP-Cron | Action Scheduler |
|---|---|---|
| Best for | Simple scheduled events | Queues and background processing |
| Runs from | Page visits or server cron trigger | Queue runners, often triggered through WP-Cron or command line |
| Failure tracking | Limited | Detailed status and logs |
| Batch handling | Weak | Strong |
| Ideal site type | Blogs and brochure sites | Stores, memberships, SaaS portals, busy plugins |
Should WP-Cron Be Disabled?
Many production sites disable the default WP-Cron trigger and replace it with a real server cron job. This does not remove WP-Cron. It simply stops WordPress from checking cron on every page load.
A server cron might call wp-cron.php every 5 minutes. That gives the site steadier timing and reduces random work during visitor requests. For busier sites, this is often the first fix before deeper queue tuning begins.
A common setup looks like this:
- Add
define('DISABLE_WP_CRON', true);towp-config.php. - Create a server cron that requests
https://example.com/wp-cron.php?doing_wp_cron. - Set the interval to 5, 10, or 15 minutes based on the site’s needs.
- Monitor scheduled tasks after the change.
This helps WP-Cron behave more predictably. It also helps Action Scheduler because many Action Scheduler runners may still depend on scheduled triggers unless a command line runner is configured.
When to Use Each One
WP-Cron is still useful. It should not be treated as broken. It is just not the right tool for every job.
Use WP-Cron when:
- The task is small and quick.
- The timing can be slightly loose.
- The job runs a few times per day or per hour.
- Failure is not business critical.
- The site has steady enough traffic or a server cron is set.
Use Action Scheduler when:
- The site has many tasks to process.
- Each task needs a clear status.
- Failures must be retried or reviewed.
- The work can be split into batches.
- The site handles orders, payments, subscriptions, or external syncs.
Performance and Reliability Tips
Good scheduling is not only about picking the right tool. Bad task design can break both systems.
- Keep jobs small: one huge task is harder to recover than 500 tiny tasks.
- Log failures: silent errors waste hours.
- Avoid duplicate scheduling: check whether an event already exists before adding it.
- Use real server cron: production sites should not rely only on random traffic.
- Watch queue size: a growing queue means processing is slower than task creation.
- Use WP CLI when possible: command line runners can handle background work more cleanly.
For example, a store that creates 2,000 queued actions overnight should not process them in one giant request. Smaller batches reduce timeout risk. They also make failed actions easier to spot.
FAQ
Is WP-Cron a real cron job?
No. WP-Cron is WordPress’s internal scheduling system. It usually runs when someone visits the site, unless a real server cron is configured to call it.
Is Action Scheduler a replacement for WP-Cron?
Not exactly. Action Scheduler is better for queues and background jobs. WP-Cron is still used for basic scheduled events and may trigger Action Scheduler runners.
Which is better for WooCommerce?
Action Scheduler is usually better for WooCommerce tasks. Orders, subscriptions, emails, and webhooks need tracking, retries, and batch processing.
Can a site use both WP-Cron and Action Scheduler?
Yes. Many WordPress sites use both. WP-Cron handles simple timing, while Action Scheduler manages heavier queued work.
How often should server cron run WP-Cron?
Many sites use 5 or 10 minutes. High-volume stores may need more frequent runs and separate queue processing through WP CLI.
Why are scheduled WordPress posts late?
The site may not have had a visit near the scheduled time. A real server cron usually fixes this issue.