cloudflare-queues

Name: cloudflare-queues
Availability: InStock
Author: Jack

Create and manage Cloudflare Queues for asynchronous background processing on Workers.

16|7|Updated Nov 20, 2025

Search Tags:#wrangler #producer #consumer #dlq #cloudflare-queues

Ready to run

npx skills add https://github.com/jackspace/ClaudeSkillz --skill cloudflare-queues-jackspace

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cloudflare-queues
Source: https://github.com/jackspace/ClaudeSkillz/tree/main/skills/cloudflare-queues
Command: npx skills add https://github.com/jackspace/ClaudeSkillz --skill cloudflare-queues-jackspace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Cloudflare Queues enable scalable, asynchronous background processing on Cloudflare Workers with reliable batching, retries, and dead-letter queues.

Core Features & Use Cases

Queue creation, producer and consumer patterns
Batching, retries, DLQ, explicit acks
Message delays, visibility, and consumer concurrency
End-to-end guidance and best practices

Quick Start

Use Wrangler CLI to create queues, implement producers and consumers, and deploy.

Frequently Asked Questions about cloudflare-queues

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I set up asynchronous message queues on Cloudflare Workers?▼

Cloudflare Queues enable asynchronous processing by letting you create producer and consumer patterns using Wrangler CLI. Producers call send() or sendBatch() to publish messages; consumers implement queue handlers that process batches with explicit ack() and retry() controls, scaling automatically across Workers.

Can I implement reliable retries and dead-letter queues with Cloudflare Queues?▼

Yes, Cloudflare Queues supports explicit retry() logic with exponential backoff and dead-letter queue (DLQ) integration for failed messages. Configure max_batch_size, max_batch_timeout, and leverage message delays up to 12 hours to handle processing failures gracefully.

What are the message size and latency limits for Cloudflare Queues?▼

Messages in Cloudflare Queues are limited to 128 KB each. Maximum message delay is up to 12 hours, and the system handles batching and concurrency auto-scaling to meet latency requirements across your serverless environment.

How do I decouple components and handle batch processing with Wrangler?▼

Use Cloudflare Queues with Wrangler to decouple producers from consumers through asynchronous batching. Producers submit tasks via send() or sendBatch(); consumers process queue(batch) events, reducing bottlenecks and enabling independent scaling of workloads.

Does Cloudflare Queues work for background task processing in serverless environments?▼

Cloudflare Queues is designed for scalable background processing on Cloudflare Workers. It decouples async workloads, supports batching with visibility controls, explicit acknowledgments, and integrates directly with the Wrangler/Workers ecosystem.