Install

Works with Drupal: ^11.2 || ^12

Using Composer to manage Drupal site dependencies

Alternative installation files

Download tar.gz 34.62 KB
MD5: 88e8ef549710de31198cfa23c13fb3d2
SHA-1: 8ec3e1fed53e1c2223152d28b11a8f059d70e60c
SHA-256: 793a99c378728ec61641ae2d7cf8be2616365ec12421d357b70778c6c22cdd5a
Download zip 56.89 KB
MD5: df7fe8a897703137eb6baf08daf3e34e
SHA-1: 6f8c90c1282ffa70c327f93185a4707137e2c7c2
SHA-256: 76d2d5dae927ccc85b3a1d3819b832518537ca09f76ed5e3878f159dae51b5f8

Release notes

A queue worker can now back off with DelayedRequeueException, and a claimed item carries its delivery attempt count. The queue's HTTP pull consumer, with its retry limit and dead-letter queue, is now managed by Cloudflare Compute 1.0.0-alpha4. Requires Drupal 11.2 or later.

Changes since 1.0.0-alpha3

  • Issue #3610175: The backend implements DelayableQueueInterface, so a worker's DelayedRequeueException delay is passed to Cloudflare under cron and drush queue:run. Cloudflare allows at most 24 hours; a longer delay is shortened to 24 hours, with a warning. Without a delay, the item is left to its lease and redelivered when that expires, as on core's queues. Every delay counts as a delivery attempt.
  • Issue #3610175: claimItem() adds attempts to the claimed item: the number of previous delivery attempts, 0 on the first. A message is delivered up to max_retries + 1 times.
  • Issue #3610175: The backend no longer creates the queue's HTTP pull consumer; Cloudflare Compute manages it from the queue asset. Queues already in use keep the consumer earlier alphas created. To give one a retry limit or a dead-letter queue, tick "Reconcile this queue's HTTP pull consumer" on its queue asset.
  • Issue #3610175: The deploy-wizard capability provisions the queue with an HTTP pull consumer and, by default, a dead-letter queue named <queue>-dlq (settings max_retries and provision_dead_letter_queue).
  • Issue #3610175: A failed push, pull, acknowledgement or delay is logged with Cloudflare's error, and a queue id that cannot be resolved is warned once with its cause, instead of failing silently (for example on a queue with no HTTP pull consumer).
  • Issue #3610175: README: retries and backoff, which outcomes spend an attempt, the attempt count, what a dead-letter queue keeps and for how long, per-environment queues (their dead-letter queues included), and upgrading. The retry limit and dead-letter queue are consumer settings, not queue settings. The Batch API builds its own queues and is not affected.
  • Issue #3610175: Requires Cloudflare Compute 1.0.0-alpha4 and Drupal 11.2 or later (^11.2 || ^12).
Created by: zach.bimson
Created on: 31 Oct 2026 at 22:45 UTC
Last updated: 31 Oct 2026 at 22:46 UTC
New features

Other releases