Skip to main content Inicio Creadores secondsky claude-skills cloudflare-queues
cloudflare-queues This skill should be used when the user asks to "set up Cloudflare Queues", "create a message queue", "implement queue consumer", "process background jobs", "configure queue retry logic", "publish messages to queue", "implement dead letter queue", or encountering "queue timeout", "message retry", "throughput exceeded", "queue backlog" errors.
Ir a la instalación Skills Marketplace Descubre y explora habilidades de IA creadas por la comunidad.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Mostrar detalles del prompt Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.
npx skills add https://github.com/secondsky/claude-skills --skill cloudflare-queuesEl comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.
¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.
Descargar Zip Descargando... Más de este repositorio Use when reworking a change to prevent tech debt, or auditing existing debt to categorize, score, and prioritize the refactor backlog.
Discover and reduce task unknowns — blindspots, missing context, and unknown unknowns — before committing to a plan, implementation, review, or merge.
MUI Base UI unstyled React components with Floating UI. Use for accessible components, Radix UI migration, render props API, or encountering positioning, popup, v1.0 rc / pre-GA issues.
Ocupaciones relacionadas SOC
Basado en la clasificación ocupacional SOC
Explorador de archivos
18 archivos name cloudflare-queues description This skill should be used when the user asks to "set up Cloudflare Queues", "create a message queue", "implement queue consumer", "process background jobs", "configure queue retry logic", "publish messages to queue", "implement dead letter queue", or encountering "queue timeout", "message retry", "throughput exceeded", "queue backlog" errors. license MIT metadata {"version":"3.0.0","wrangler_version":"4.81.0","workers_types_version":"4.20260408.0","last_verified":"2025-12-27","errors_prevented":10,"templates_included":6,"references_included":11,"agents_included":2,"commands_included":3,"keywords":["cloudflare queues","queues workers","message queue","queue bindings","async processing","background jobs","queue consumer","queue producer","batch processing","dead letter queue","dlq","message retry","queue ack","consumer concurrency","queue backlog","wrangler queues"]}
Cloudflare Queues
Status : Production Ready ✅ | Last Verified : 2025-12-27
Dependencies : cloudflare-worker-base (for Worker setup)
Contents : Quick Start • Critical Rules • Top Errors • Use Cases • When to Load References • Limits
Quick Start (10 Minutes)
1. Create Queue
bunx wrangler queues create my-queue
bunx wrangler queues list
2. Producer (Send Messages) {
"name" : "my-producer" ,
"main" : "src/index.ts" ,
"queues" : {
"producers" : [
{
"binding" : "MY_QUEUE" ,
"queue" : "my-queue"
}
]
}
}
import { Hono } from 'hono' ;
type Bindings = {
MY_QUEUE : Queue ;
};
const app = new Hono <{ Bindings : Bindings }>();
app.post ('/send' , async (c) => {
await c.env .MY_QUEUE .send ({
userId : '123' ,
action : 'process-order' ,
timestamp : Date .now (),
});
return c.json ({ status : 'queued' });
});
export default app;
3. Consumer (Process Messages) {
"name" : "my-consumer" ,
"main" : "src/consumer.ts" ,
"queues" : {
"consumers" : [
{
"queue" : "my-queue" ,
"max_batch_size" : 10 ,
"max_retries" : 3 ,
"dead_letter_queue" : "my-dlq"
}
]
}
}
import type { MessageBatch } from '@cloudflare/workers-types' ;
export default {
async queue (batch : MessageBatch ): Promise <void > {
for (const message of batch.messages ) {
console .log ('Processing:' , message.body );
}
},
};
Load : references/setup-guide.md for complete 6-step setup with DLQ configuration
Critical Rules
Always Do ✅
Configure Dead Letter Queue for production queuesUse explicit ack() for non-idempotent operations (DB writes, API calls)Validate message size before sending (<128 KB)Use sendBatch() for multiple messages (more efficient)Implement exponential backoff for retriesSet appropriate batch settings based on workloadMonitor queue backlog and consumer errorsUse ctx.waitUntil() for async cleanup in consumersHandle errors gracefully - log, alert, retryLet concurrency auto-scale (don't set max_concurrency unless needed)
Never Do ❌
Never assume message ordering - not guaranteed FIFONever rely on implicit ack for non-idempotent ops - use explicit ack()Never send messages >128 KB - will failNever delete queues with active messages - data lossNever skip DLQ configuration in productionNever exceed 5000 msg/s per queue - rate limit errorNever process messages synchronously in loop - use Promise.all()Never ignore message.attempts - use for backoff logicNever set max_concurrency=1 unless you have a very specific reasonNever forget to ack() in explicit acknowledgement patterns
Top 3 Critical Errors
Error #1: Message Too Large Problem : Message exceeds 128 KB limit
Solution : Store large data in R2, send reference
await env.MY_QUEUE .send ({ data : largeArray });
const message = { data : largeArray };
const size = new TextEncoder ().encode (JSON .stringify (message)).length ;
if (size > 128000 ) {
const key = `messages/${crypto.randomUUID()} .json` ;
await env.MY_BUCKET .put (key, JSON .stringify (message));
await env.MY_QUEUE .send ({ type : 'large-message' , r2Key : key });
} else {
await env.MY_QUEUE .send (message);
}
Error #2: Throughput Exceeded Problem : Exceeding 5000 messages/second per queue
Solution : Use sendBatch() and rate limiting
for (let i = 0 ; i < 10000 ; i++) {
await env.MY_QUEUE .send ({ id : i });
}
const messages = Array .from ({ length : 10000 }, (_, i ) => ({
body : { id : i },
}));
for (let i = 0 ; i < messages.length ; i += 100 ) {
await env.MY_QUEUE .sendBatch (messages.slice (i, i + 100 ));
}
Error #3: Entire Batch Retried When One Message Fails Problem : Single message failure causes all messages to retry
Solution : Use explicit acknowledgement
export default {
async queue (batch : MessageBatch , env : Env ): Promise <void > {
for (const message of batch.messages ) {
await env.DB .prepare ('INSERT INTO orders VALUES (?, ?)' ).bind (
message.body .id ,
message.body .amount
).run ();
}
},
};
export default {
async queue (batch : MessageBatch , env : Env ): Promise <void > {
for (const message of batch.messages ) {
try {
await env.DB .prepare ('INSERT INTO orders VALUES (?, ?)' ).bind (
message.body .id ,
message.body .amount
).run ();
message.ack ();
} catch (error) {
console .error (`Failed: ${message.id} ` , error);
}
}
},
};
Load references/error-catalog.md for all 10 errors including DLQ configuration, auto-scaling issues, message deletion prevention, and detailed solutions.
Common Use Cases
Use Case 1: Basic Message Queue When : Simple async job processing (emails, notifications)
await env.MY_QUEUE .send ({ type : 'email' , to : 'user@example.com' });
export default {
async queue (batch : MessageBatch ): Promise <void > {
for (const message of batch.messages ) {
await sendEmail (message.body .to , message.body .content );
}
},
};
Load : templates/queues-producer.ts + templates/queues-consumer-basic.ts
Use Case 2: Database Writes (Non-Idempotent) When : Writing to database, must avoid duplicates
Load : templates/queues-consumer-explicit-ack.ts + references/consumer-api.md
Use Case 3: Retry with Exponential Backoff When : Calling rate-limited APIs, temporary failures
Load : templates/queues-retry-with-delay.ts + references/error-catalog.md (Error #2, #3)
Use Case 4: Dead Letter Queue Pattern When : Production systems, need to capture permanently failed messages
Load : templates/queues-dlq-pattern.ts + references/setup-guide.md (Step 4)
Use Case 5: High Throughput Processing When : Processing thousands of messages per second
{
"queues" : {
"consumers" : [ {
"queue" : "my-queue" ,
"max_batch_size" : 100 ,
"max_batch_timeout" : 5 ,
"max_concurrency" : null } ]
}
}
Load : references/best-practices.md → Optimizing Throughput
When to Load References Load references/setup-guide.md when :
User needs complete setup walkthrough (queue → producer → consumer → DLQ)
First time setting up Cloudflare Queues
Need production configuration examples
Want complete end-to-end example
Load references/error-catalog.md when :
Encountering any of the 10 documented errors
Troubleshooting queue issues
Messages not being delivered/processed
Need prevention checklist
Load references/producer-api.md when :
Need complete producer API reference
Using send() or sendBatch() methods
Need message format specifications
Handling large messages or batches
Load references/consumer-api.md when :
Need complete consumer API reference
Using explicit ack(), retry(), or retryAll()
Need batch processing patterns
Implementing complex consumer logic
Load references/best-practices.md when :
Optimizing queue performance
Production deployment guidance
Monitoring and observability setup
Security and reliability patterns
Load references/wrangler-commands.md when :
Need CLI commands reference
Managing queues (create, delete, list)
Controlling delivery (pause, resume)
Debugging queue issues
Real-time monitoring and performance analysis
Load references/typescript-types.md when :
Need complete TypeScript type definitions
Working with Queue, MessageBatch, or Message interfaces
Implementing type-safe producers or consumers
Using generic types for message bodies
Need type guards for message validation
Load references/production-checklist.md when :
Preparing for production deployment
Need pre-deployment verification checklist
Want detailed explanations of production best practices
Setting up monitoring, DLQ, or error handling
Planning load testing or security review
Load references/pull-consumers.md when :
Need to consume messages from non-Workers environments
Integrating with existing backend services (Node.js, Python, Go)
Implementing pull-based polling instead of push-based consumption
Working with containerized or legacy applications
Load references/http-publishing.md when :
Publishing messages from external systems via HTTP
Integrating webhooks from third-party services
Need to send messages without deploying Workers
Implementing CI/CD pipeline notifications
Load references/r2-event-integration.md when :
Triggering queue messages on R2 bucket events
Implementing automated image/document processing
Setting up event-driven data pipelines
Need R2 object upload/delete notifications
Agents & Commands
queue-debugger - 9-phase diagnostic analysis for queue issues (systematic troubleshooting)queue-optimizer - Performance tuning and cost optimization (batch size, concurrency, retries)
/queue-setup - Interactive wizard for complete queue setup/queue-troubleshoot - Quick diagnostic for common issues/queue-monitor - Real-time metrics and status display
Limits & Quotas
Message size : 128 KB max per messageThroughput : 5,000 messages/second per queueBatch size : 100 messages max per sendBatch()Consumer CPU time : 30 seconds (default), 300 seconds (max with config)Max retries : Configurable (default 3)Queue name : Max 63 characters, lowercase/numbers/hyphens Load references/best-practices.md for handling limits and optimization strategies.
Configuration Reference Producer : Add queue binding to wrangler.jsonc queues.producers array with binding and queue fields.
Consumer : Configure in wrangler.jsonc queues.consumers array with queue, max_batch_size (1-100), max_batch_timeout (0-60s), max_retries, dead_letter_queue, and optionally max_concurrency (default: auto-scale).
CPU Limits : Increase limits.cpu_ms from default 30,000ms if processing takes longer.
Load references/setup-guide.md for complete configuration examples and templates/wrangler-queues-config.jsonc for production-ready config.
Using Bundled Resources
References (references/)
setup-guide.md - Complete 6-step setup (queue → producer → consumer → DLQ → deploy → production config)error-catalog.md - All 10 errors with solutions + prevention checklistproducer-api.md - Complete producer API (send, sendBatch, message format)consumer-api.md - Complete consumer API (ack, retry, batch processing)best-practices.md - Performance, monitoring, security, reliability patternswrangler-commands.md - CLI reference (create, delete, list, pause, resume)typescript-types.md - Complete TypeScript type definitions for Queue, MessageBatch, Messageproduction-checklist.md - Pre-deployment verification and best practicespull-consumers.md - Pull-based consumers for non-Workers environments (HTTP polling)http-publishing.md - Publishing messages via HTTP API from external systemsr2-event-integration.md - R2 event notifications triggering queue messages
Templates (templates/)
queues-producer.ts - Basic producer with single and batch sendingqueues-consumer-basic.ts - Implicit ack consumer (idempotent operations)queues-consumer-explicit-ack.ts - Explicit ack consumer (non-idempotent)queues-retry-with-delay.ts - Exponential backoff retry patternqueues-dlq-pattern.ts - Dead letter queue setup and consumerwrangler-queues-config.jsonc - Complete production configuration
TypeScript Types Use @cloudflare/workers-types package for complete type definitions: Queue, MessageBatch<Body>, Message<Body>, QueueSendOptions.
Load references/typescript-types.md for complete type reference with interfaces, generics, type guards, and usage examples.
Monitoring & Debugging Key Commands : wrangler queues info (status), wrangler tail (logs), wrangler queues pause-delivery/resume-delivery (control).
Load references/wrangler-commands.md for complete CLI reference with real-time monitoring, debugging workflows, and performance analysis commands.
Production Checklist 12-Point Pre-Deployment Checklist : DLQ configuration, message acknowledgment strategy, size validation, batch optimization, concurrency settings, CPU limits, error handling, monitoring, rate limiting, idempotency, load testing, and security review.
Load references/production-checklist.md for complete checklist with detailed explanations, code examples, and deployment workflow.
Related Skills
cloudflare-worker-base - Worker setup and configurationcloudflare-d1 - Database integration for queue consumerscloudflare-r2 - Store large message payloadscloudflare-workflows - More complex orchestration needs
Official Documentation
Check references/error-catalog.md for all 10 errors and solutions
Review references/setup-guide.md for complete setup walkthrough
See references/best-practices.md for production patterns
Check official docs: https://developers.cloudflare.com/queues/
