WP Queue Process
Non-blocking background jobs for WordPress.
- Non-blocking async requests and background queue processing
- Swappable storage driver for where the queue lives
- Server-load-aware batching so it backs off under pressure
- A self-healing cron that recovers stalled queues
- License
- GPL-2.0-or-later
- Language
- PHP
About WP Queue Process
Async requests and background queue processing for WordPress — a swappable storage driver, load-aware batching, and a self-healing cron.
What it does
WP Queue Process runs long or repetitive work outside the request cycle, so a WordPress page never blocks waiting on it. Jobs are batched with an eye on server load, persisted through a swappable storage driver, and kept alive by a cron that heals itself if a queue stalls.
Install with Composer:
composer require foxelabs/wp-queue-processFrequently asked questions
How do I run background jobs in WordPress?
Install WP Queue Process with `composer require foxelabs/wp-queue-process`, push items onto a queue, and it processes them in non-blocking async requests instead of holding up the page load. A self-healing cron picks the queue back up if a batch stalls.
How is this different from WP Background Processing?
It covers the same ground — async requests and batched queue processing — with a swappable storage driver so the queue does not have to live in the options table, load-aware batching that backs off when the server is under pressure, and a cron that recovers stalled queues on its own.
Where is the queue stored?
Behind a storage driver, so you choose. The default keeps things in WordPress, and the interface lets you point it at a custom table or another store without touching the processing logic — which also makes the library straightforward to test.
Does it need WP-Cron to be enabled?
Processing runs over async HTTP requests, so the work does not depend on cron firing. Cron is used as the safety net that restarts a queue which stopped mid-run.
Learn how we can help you build better.
Questions about a plugin, a licence, or an expert advisor — ask and get a straight answer from the team that wrote the code.