cloudflare-queues

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

961|99|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/jezweb/claude-skills --skill cloudflare-queues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloudflare-queues
Source: https://github.com/jezweb/claude-skills/tree/main/skills/cloudflare-queues
Command: npx skills add https://github.com/jezweb/claude-skills --skill cloudflare-queues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires cloudflare-worker-base, and includes references (resource) components.

What problem does it solve?

This Skill eliminates the complexity of implementing reliable asynchronous processing, allowing you to decouple application components and handle background jobs without manual intervention.

Core Features & Use Cases

  • Queue Creation & Management: Easily create, configure, and monitor queues with simple CLI commands.
  • Production-Ready Patterns: Includes dead letter queues, exponential backoff, and explicit acknowledgement for non-idempotent operations.
  • Use Case: Imagine you need to process 10,000 user registration emails. Use this Skill to automatically queue and process them in the background while your application remains responsive.

Quick Start

Create a queue named 'email-tasks' and send a message to process a welcome email for user ID 123.

Frequently Asked Questions about cloudflare-queues

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

FAQPage Schema
How do I build async message queues in Cloudflare Workers?

Async message queues in Cloudflare Workers decouple application components by enabling producer-consumer patterns. Create queues using CLI commands, send messages up to 128 KB, batch up to 100 messages, and configure retry strategies with exponential backoff for reliable background processing.

What's the best way to process background jobs without blocking my application?

Use asynchronous background processing to queue tasks separately from request handling. Cloudflare Queues lets you defer work like email sending or data processing with explicit acknowledgement support, keeping your application responsive while jobs process independently.

Can I implement dead letter queues and retry logic with Cloudflare Queues?

Yes. Cloudflare Queues supports production-ready patterns including dead letter queues for failed messages, exponential backoff retry strategies, and maximum delays up to 12 hours, enabling reliable handling of failed or problematic jobs.

Do I need explicit acknowledgement for non-idempotent operations in message queues?

Explicit acknowledgement support ensures non-idempotent operations process exactly once. Cloudflare Queues provides this mechanism so you control when messages are considered successfully processed, preventing duplicate execution of critical tasks.

What are the size and concurrency limits when using Cloudflare Queues for batch processing?

Cloudflare Queues enforces a maximum message size of 128 KB and batch size limits of up to 100 messages per operation. These constraints shape your message design and batch strategy for efficient concurrent processing.

How do I handle message delays in Cloudflare Queues?

Cloudflare Queues supports maximum message delays up to 12 hours, letting you schedule background job execution. This enables time-based workflows like delayed notifications or scheduled batch processing without external scheduling tools.