內容簡介
AMPM Queue Manager for Action Scheduler 讓網站管理員能夠安全且精細地控制 WordPress Action Scheduler 的行為，無需編輯程式碼，適合用於 WooCommerce 等外掛的背景處理。
【主要功能】
• 直觀的管理介面，輕鬆調整設定
• 顯示當前佇列狀態，便於監控
• 手動執行佇列，限制處理量
• 自適應 AJAX 清理舊的完成或失敗的任務
• 提供明確的確認警告，避免誤操作
外掛標籤
開發者團隊
② 後台搜尋「AMPM Queue Manager for Action Scheduler」→ 直接安裝（推薦）
原文外掛簡介
AMPM Queue Manager for Action Scheduler gives site administrators fine-grained, safe control over WordPress Action Scheduler behavior — without editing code.
Action Scheduler powers background processing in WooCommerce, Mailchimp, Jetpack, and dozens of other plugins. Its default settings are tuned for medium-to-large environments and can overwhelm shared hosting servers, causing slow page loads, server timeouts, and database bloat.
This plugin lets you tune key parameters from a clean admin panel (Settings → Queue Manager), with pre-selected recommended values and plain-language descriptions of each trade-off.
The Tools tab shows the current queue status, provides a deliberately limited manual queue run, links to the Action Scheduler administration screen, and includes an adaptive AJAX cleaner for old completed, failed, or canceled actions.
Compatibility
Requires WordPress 5.8 or newer.
Requires PHP 7.2 or newer.
Version 1.0.1 was confirmed working with WordPress 7.0.2 and Action Scheduler 3.9.3.
Tools: Queue Status and Manual Run
See pending, currently due, in-progress, and recently failed actions at a glance. If work is waiting, an administrator can start one conservative processing cycle limited to one runner, batches of 25 actions, and a 20-second runner time limit.
Because due actions can send email, process orders, or contact external services, the manual run requires explicit confirmation. A direct link opens the standard Action Scheduler administration screen, using the WooCommerce-integrated location when WooCommerce is active.
The queue status also reports the total number of failed actions and how many failed during the last 24 hours. Administrators can permanently delete all failed actions and their related logs in conservative batches after reviewing a clear confirmation warning.
Tools: Adaptive Action Scheduler Purge
Action Scheduler default cleanup routines often fail to process massive backlogs on old stores, leaving hundreds of thousands of orphaned rows.
The plugin includes a dedicated Tools tab providing an immediate, on-demand Action Scheduler DB cleanup.
* Adaptive Batching: Safely deletes old records using an intelligent AJAX loop that self-tunes its chunk size (up to 10,000 items per request) based on your server’s real-time response capability.
* Zero-Timeout Architecture: Built-in 504 Gateway Timeout detection automatically halts and retries with a smaller payload, ensuring large databases (50k+ rows) can be cleared on any hosting plan without crashing.
* Feedback & Safety: Shows real-time granular progress and requires explicit database-backup confirmation before starting the irreversible cleanup.
Action Scheduler Settings
Concurrent Batches
Controls how many batches of background jobs can run at the same time.
Default: 5. On shared hosting, 5 simultaneous batches can spike CPU and memory usage, triggering server-level throttling or timeouts. Setting this to 1 ensures only one batch runs at a time, protecting server resources — at the cost of slower queue processing.
Jobs per Batch
Controls how many individual jobs (actions) are processed in each batch run.
Default: 25. Lowering this reduces peak memory usage. Raising it speeds up queue processing on capable servers but risks PHP memory limit errors on constrained environments.
Time Limit per Run
Controls the maximum seconds a queue runner is allowed to execute before stopping.
Default: 30 seconds. When running only 1 concurrent batch, the 30-second default may not be enough to drain large queues. Increasing to 60 or 90 seconds lets each run do more work without needing additional concurrency.
Log Retention Period
Controls how long completed and failed action records are kept in the database.
Default: 30 days. On busy stores, the Action Scheduler log can grow to hundreds of thousands of rows. Reducing retention to 7 or 14 days keeps the database lean without losing meaningful debugging history for most use cases.
WooCommerce Settings
Product Loop Transient Expiration
Controls how long WooCommerce caches product loop data (wc_product_loop_* transients) in the database.
Default: 30 days. These transients accumulate per product ID and can bloat the wp_options table significantly. Reducing to 1 day keeps the cache fresh and the database tidy, with minimal performance impact since WooCommerce regenerates them efficiently.
Cart Fragments
Controls whether WooCommerce fires an AJAX request on every page load to update the mini-cart widget in real time.
Default: Enabled. This AJAX call adds latency to every page view. If your theme does not display a live mini-cart that updates instantly (e.g. you use a simple cart icon that links to /cart), disabling fragments eliminates an unnecessary request per visitor. The cart page and checkout are not affected.
