Cloudflare Queues

Global at-least-once message queue consumed by Workers, with batching and dead letter queues.

Provider: cloudflare
Kind: Queue
Category: Messaging
Official docs: https://developers.cloudflare.com/queues/platform/limits/

Properties · 9 set by this component

property	type	values	required	kind default	this component
backoff	enum	none \| fixed \| exponential \| exponential-jitter	no	—	inherited
consumerType · component property	enum	push \| pull	no	push	inherited
deadLetterQueue	boolean	—	no	false	▸ false
delivery	enum	at-most-once \| at-least-once \| exactly-once	yes	—	▸ at-least-once
instances	integer	—	no	—	inherited
managed	boolean	—	no	false	▸ true
maxAttempts	integer	—	no	—	▸ 3
maxBatchSize · component property	integer	—	no	100	inherited
maxConsumerConcurrency · component property	integer	—	no	250	inherited
maxMessageSizeKb · component property	integer	—	no	128	inherited
maxRetentionDays · component property	integer	—	no	14	inherited
ordering	enum	none \| per-key \| global	no	none	▸ none
persistence	boolean	—	no	true	▸ true
replay	boolean	—	no	false	▸ false
retentionDays	integer	—	no	—	▸ 1
role	enum	work \| dlq \| retry \| offline-mailbox \| frontier	no	work	▸ work

Rules that apply · 3

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

Queue without dead-letter queueerror

queue-missing-dlq

A queue that receives asynchronous traffic and has no dead-letter queue either drops poison messages or retries them forever. Neither outcome leaves anything for a human to investigate.

— all of these hold:
— the node's `deadLetterQueue` is false
— the node has at least one asynchronous incoming edge

Retry queue without dead-letter queueerror

retry-queue-without-dlq

A retry queue is where poison messages end up. With no dead-letter queue they are retried forever or dropped in silence, and nobody ever looks at the failed payment.

— all of these hold:
— the node's `role` is "retry"
— the node's `deadLetterQueue` is false

Retry queue without backoffwarning

retry-without-backoff

Retrying a transient failure at full speed turns one slow dependency into a retry storm. A retry queue backs off, preferably exponentially and with jitter.

— all of these hold:
— the node's `role` is "retry"
— any of these hold:
— the node's `backoff` has no value
— the node's `backoff` is "none"

Use it in a design

nodes:
  - { id: "queues", component: "cloudflare-queues" }

Source

1# yaml-language-server: $schema=../../schema/component.schema.json
2# Cloudflare Queues: a global message queue consumed by Workers. "Delivery guarantees" states at
3# least once delivery; "Queues - Limits" gives the 24 hour default retention (up to 14 days) and the
4# 100 message batch, and "Dead letter queues" states no DLQ is attached until one is configured.
5schemaVersion: "1"
6type: "component"
7id: "cloudflare-queues"
8kind: "queue"
9provider: "cloudflare"
10docs: "https://developers.cloudflare.com/queues/platform/limits/"
11defaults:
12  managed: true
13  delivery: "at-least-once"
14  ordering: "none"
15  deadLetterQueue: false
16  replay: false
17  persistence: true
18  retentionDays: 1
19  maxAttempts: 3
20  role: "work"
21properties:
22  maxBatchSize:
23    type: "integer"
24    default: 100
25  maxMessageSizeKb:
26    type: "integer"
27    default: 128
28  maxConsumerConcurrency:
29    type: "integer"
30    default: 250
31  consumerType:
32    type: "enum"
33    values: ["push", "pull"]
34    default: "push"
35  maxRetentionDays:
36    type: "integer"
37    default: 14

The same page as markdown, for an agent: /catalogue/components/cloudflare-queues.md