This project is not covered by Drupal’s security advisory policy.
Run Drupal's queue system on Cloudflare Queues with no code changes. Opt a queue (cron queues, the Batch API, or a custom queue worker) onto the Cloudflare backend in settings.php, and items are enqueued and consumed over the Cloudflare Queues HTTP pull/ack API.
Cloudflare Queues is a managed, global message queue. Unlike most queue backends, you do not stand up or wire a broker: the queue is provisioned and tracked for you by the Cloudflare Compute module, and this module runs Drupal's queue on it.
Features
- Implements Drupal's ReliableQueueInterface and DelayableQueueInterface, so existing queue workers run unchanged and can back off with DelayedRequeueException.
- Consumes a queue provisioned and tracked by Cloudflare Compute (its id and credentials come from the queue asset); no broker to operate.
- At-least-once delivery over the Cloudflare Queues HTTP pull/ack API, with visibility-timeout leases and retries.
- Retries and dead letters follow the queue's HTTP pull consumer, which Cloudflare Compute manages from the queue asset (retry limit and dead-letter queue).
- Swappable payload codec: JSON by default, or an opt-in PHP-serialize codec that preserves object payloads.
Post-Installation
- Register the Cloudflare queue on Cloudflare Compute's Cloudflare Queues page (Configuration > Web services > Cloudflare Queues), or provision it in code through this module's cloudflare_queue_backend capability with the Cloudflare SDK's reconciler. On the queue's form, tick 'Reconcile this queue's HTTP pull consumer' and set a retry limit and a dead-letter queue.
- Opt a Drupal queue onto the backend in settings.php, for example:
$settings['queue_service_my_worker'] = 'queue.cloudflare'; - Optionally change the Cloudflare queue-name prefix (default "drupal-") in the module settings.
Additional Requirements
Requires Drupal 11.2 or later, the Cloudflare API (cloudflare_api), Cloudflare SDK (cloudflare_sdk) and Cloudflare Compute (cloudflare_compute) modules, and a Cloudflare API token with Queues Edit permission (queues#read and queues#write). While the suite is in alpha, install it together with its alpha dependencies:
composer require drupal/cloudflare_queue:^1.0@alpha drupal/cloudflare_compute:^1.0@alpha drupal/cloudflare_sdk:^1.0@alpha drupal/cloudflare_api:^1.0@alpha
Composer applies a stability flag such as @alpha only to packages the root composer.json requires, so on a site with minimum-stability: stable, requiring this module alone fails. Alternatively, allow alpha releases site-wide with minimum-stability: alpha and prefer-stable: true.
Recommended modules/libraries
None beyond the required dependencies. Cloudflare Compute (a hard dependency) provisions and tracks the queue this backend runs on.
Similar projects
Like the core database queue, or backends such as RabbitMQ and AWS SQS, this provides a Drupal queue implementation. The difference is provisioning: the queue is created and tracked for you as configuration (by Cloudflare Compute), and it runs over Cloudflare's global HTTP API with no broker or separate worker to operate.
Supporting this Module
Issue reports, patches and feedback are welcome in the project's issue queue.
Community Documentation
- Cloudflare Queues: https://developers.cloudflare.com/queues/
- Pull consumers: https://developers.cloudflare.com/queues/configuration/pull-consumers/
Project information
- Project categories: Integrations
- Ecosystem: Cloudflare SDK
- By zach.bimson on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.

