Action Scheduler is a library for timing and running background tasks in WordPress, and is used by WooCommerce and many plugins. Webhook sending, email processing, extension, sync and erasing can be in the form of action in a row. The size of the row number is not alone; the status, age, hook, and speed of the input and output determines whether you have a real backlog.
Short answer:Each action has a hook, runtime, status, group, and argument. The runner claims and executes the finished tasks and records the result. If the producer creates a faster than the consumer action, cron is not executed, callback errors are made, or tasks are long, the row grows.
Why does Wocomers need to line up?
Some tasks do not need to hold the Checkout response or the Control Panel. The row allows the operation to run later, with retry and history. This reduces user latency separation, but only when the regular runner, actions are idempotent and errors are visible.
The main components of an Action
| Part of it. | What does it mean? | Diagnostic use |
|---|---|---|
| Hook | The name of the work to be done. | Additional ownership and type of operation |
| Arguments | Callback entry | Sample detection and repetition; may be sensitive |
| Group | Logical class of actions | The producer split. |
| Scheduled date | Time to plan. | Calculate the age of the backlog |
| Status | Running cycle stage | The separation of expectation, execution and failure |
| Log | Lifecycle events | Time of claim, completion or exception |
What do the circumstances say?
- Pending:It's scheduled or ready to go.
- In-progress:Claimed by the runner and considered to be in process.
- Complete:Callback is completed without recorded error.
- Failed:Exception or failure execution is recorded.
- Canceled:Action canceled and cannot be executed.
The name and details of the situation may depend on the version of the interface. Complete is not always a guarantee of final commercial success; callback may be complete without exception, but the external API may have given an unwanted result.
How do Runner and Claim work?
Runner claims a limited set of ready actions so that other workers do not do the same at the same time. Then callbacks are executed and the status is recorded. If the process stops in the middle of the batch, the claim or action in progress may require a version logic recovery. Removing the lock and claim manually can create a simultaneous execution.
Connection with wp-cron
The Action Scheduler for runner startup usually relies on the WordPress timing and site requests installer, although the hosting architecture can have real cron. If wp-cron is disabled but the correct platform replacement is not running, action remains ready.wp-cron and resource consumptionIt explains the difference in timing and execution.
Why is the Complete increasing?
The post-transaction store is a natural one that produces a lot of complete history. The main problem may be that retention/cleanup is not implemented, not the operational backlog. See oldest complete and growth trend.
Why is Pending increasing?
- It's not time to execute them yet.
- Runner or cron is not running.
- The production rate is greater than the consumption capacity.
- A slow or locked hook holds back the batch.
- PHP is a rich database or external API.
- The defective plugin continuously schedules the same action.
For the actual incident, the guide.Thousands of Scheduled Action pending.It has a phase detection pathway.
How do we read failures?
A failure caused by deleted data is different from thousands of timeout APIs. Manual retry without removing the cause can cause repetitive pressure and side effects. Credential, payload, stock, payment, and webhook may contain sensitive data; redact the log before sharing.
Recurring Action is different from Recurring Action.
A conscious recurring action will schedule the next sample at a specified interval. But the defective plugin may re-create the same work at each page load. Compare hook, args, and time intervals. Removing all samples may stop the necessary extension or sync; the producer and uniqueness rules must be corrected.
Order and dependency of operations
The existence of the row itself does not guarantee the order of business. If the second action depends on the first result, then the order sync example after payment confirmation must be clear. The manual execution of the out-of-order actions can contradict the destination data. Timestamp is not the only measure of dependence; the order and state identifier must also be checked.
For standalone tasks concurrency is useful, but actions of an entity may require lock or serialization. The lock must have a specific timeout and recovery so that the crash does not stop all subsequent tasks.
Why is idempotency vital?
Runner, retry, and network failure can enter callback more than once. Sensitive operations must be checked with a single ID and current status to avoid duplication of the item, email, payment, or webhook.
How does a row affect speed?
The jobs share the user requests of CPU, RAM, PHP worker, I/O, and database. Heavy batch in sales hours may slow Checkout. On the other hand, excessive reduction in runner backlog capacity increases.
A simple model of capacity.
Compare the action input rate to the completion rate in the same interval. If 100 new actions and only 60 are completed per minute, the backlog will grow even without error. The median and p95 of the hook duration, not just the number, indicate the required capacity.
View from the Walkcomers panel
The Scheduled Actions section usually allows you to filter status, hook, group and log view. First, record read-only checks and samples. Manual execution or group cancellation on production is a transformative operation and should have a clear business effect. Avoid displaying sensitive args in a public screenshot.
Privacy and data security.
The action argument may keep the customer ID, order, webhook URL or part of the payload. Secret and token should not be registered as visible arguments or logs; limited reference and credential recovery are more appropriate. Limit row panel access to the required roles as manual execution of a hook can create actual operations.
WP-CLI and the command line tool
The functionality of the commands depends on the version of the Action Scheduler and the plugins installed; see the same environment before running help. Listing commands are useful for inventory, but run/delete a category can cause sudden loads or deletions. Test on clone and with limited batch.
Monitoring is right on line.
- Number of pending run-ready and age oldest case
- Schedule and complete rate based on hook
- Failure rate and exception prevail
- P50/P95 callback time
- Old in-progress and unusual claims
- PHP queue, DB latency and external API simultaneously
Hundreds of actions for the future may be normal, but ten critical actions that are two hours past their deadline are a major problem.
Safe and sound.
- Document the owner of each hook and the importance of the business.
- Define the complete/failed retention.
- Monitor runner and cron with health check.
- Design callbacks idempotent and with reasonable timeout.
- Set a time limit and rate limit for heavy loads.
- After the update, compare the error rate and backlog to the baseline.
Common Mistakes
- Delete all Action Scheduler tables
- One knowing complete history and pending backlog
- Running all the pendings in one big batch
- Retry fail without reading exception
- Manipulating claims and locks with SQL
- Increased concurrency without PHP/MySQL capacity
- Ignoring the side effects of payment and cash
When do you need special assistance?
If the row includes a payment, subscription, inventory, or ERP sync and the runner is backward, removing or manually executing can double the operation.Support for the WooCommerce storeIt can design hook, input/output rate, cron and controlled resource analysis and recovery.
Common Questions
Is it normal to have too many Scheduled Action?
Depending on the situation and age, the future and the complete history are not the same as the backward pending.
Can we delete all the Complete?
Use retention and audit requirements and supported cleanup; direct removal is not recommended.
Why is Action running again?
Retry, repeat callback, or multiple producer may be the factor; idempotency of callback should also be considered.
Is the Action Scheduler the same as wp-cron?
No, it has its own lifecycle, but runner start is usually associated with the WordPress cron engine.