AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

cloudflare

Discover and choose Cloudflare products for apps, APIs, AI agents, storage, networking, and security. Use for architecture and product selection, including when the user describes a need without naming a Cloudflare product; then find the relevant skill or documentation.

Original source
cloudflare
License
Apache-2.0
Pinned revision
e44f580f9c4fa3bf268e284ae7706c7954ba31fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read cloudflare--cloudflare at revision e44f580f9c4fa3bf268e284ae7706c7954ba31fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 135

references/queues/api.md

Queues API Reference

Fetch the current API documentation for the operation being implemented; do not infer signatures, payloads, or acknowledgement rules from old examples.

| Task | Documentation | |------|---------------| | Send individual messages or batches; choose encoding; implement a typed Worker queue handler; dispatch by queue name | JavaScript APIs | | Understand automatic acknowledgement, explicit per-message and batch actions, precedence, delivery failures, delays, and backoff | Batching, retries, and delays | | Pull over HTTP and acknowledge or retry using leases | Pull consumers | | Publish from outside Workers | Publish to a Queue via HTTP |

Acknowledge only after the intended work succeeds. For independently processed messages, use per-message outcomes to avoid replaying successful work when another message fails. If catching an error and continuing, explicitly request a retry for work that still needs processing; a successful handler return can acknowledge messages automatically. Fetch the linked acknowledgement rules before mixing message-level and batch-level actions.

Await required work, including downstream writes or sends, before acknowledging it. Check the JavaScript API's handler lifecycle rules before using waitUntil(); background work is not independent of delivery success.

See configuration.md for bindings and consumer setup, and gotchas.md for delivery diagnostics.