---
title: Queues Changelog
image: https://developers.cloudflare.com/cf-twitter-card.png
---

[Skip to content](#%5Ftop) 

# Changelog

New updates and improvements at Cloudflare.

[ Subscribe to RSS ](https://developers.cloudflare.com/changelog/rss/index.xml) [ View RSS feeds ](https://developers.cloudflare.com/fundamentals/new-features/available-rss-feeds/) 

Queues

![hero image](https://developers.cloudflare.com/_astro/hero.CVYJHPAd_26AMqX.svg) 

Feb 04, 2026
1. ### [Cloudflare Queues now available on Workers Free plan](https://developers.cloudflare.com/changelog/post/2026-02-04-queues-free-plan/)  
[ Queues ](https://developers.cloudflare.com/queues/)  
[Cloudflare Queues](https://developers.cloudflare.com/queues) is now part of the Workers free plan, offering guaranteed message delivery across up to **10,000 queues** to either [Cloudflare Workers](https://developers.cloudflare.com/workers) or [HTTP pull consumers](https://developers.cloudflare.com/queues/configuration/pull-consumers). Every Cloudflare account now includes **10,000 operations per day** across reads, writes, and deletes. For more details on how each operation is defined, refer to [Queues pricing ↗](https://developers.cloudflare.com/workers/platform/pricing/#queues).  
All features of the existing Queues functionality are available on the free plan, including unlimited [event subscriptions](https://developers.cloudflare.com/queues/event-subscriptions/). Note that the maximum retention period on the free tier, however, is 24 hours rather than 14 days.  
If you are new to Cloudflare Queues, follow [this guide ↗](https://developers.cloudflare.com/queues/get-started/) or try one of our [tutorials](https://developers.cloudflare.com/queues/tutorials/) to get started.

Jan 09, 2026
1. ### [Get notified when your Workers builds succeed or fail](https://developers.cloudflare.com/changelog/post/2025-12-11-builds-event-subscriptions/)  
[ Workers ](https://developers.cloudflare.com/workers/)[ Queues ](https://developers.cloudflare.com/queues/)  
You can now receive notifications when your Workers' builds start, succeed, fail, or get cancelled using [Event Subscriptions](https://developers.cloudflare.com/queues/event-subscriptions/).  
[Workers Builds](https://developers.cloudflare.com/workers/ci-cd/builds/) publishes events to a [Queue](https://developers.cloudflare.com/queues/) that your Worker can read messages from, and then send notifications wherever you need — Slack, Discord, email, or any webhook endpoint.  
You can deploy [this Worker ↗](https://github.com/cloudflare/templates/tree/main/workers-builds-notifications-template) to your own Cloudflare account to send build notifications to Slack:  
[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/cloudflare/templates/tree/main/workers-builds-notifications-template)  
The template includes:  
   * Build status with Preview/Live URLs for successful deployments  
   * Inline error messages for failed builds  
   * Branch, commit hash, and author name  
![Slack notifications showing build events](https://developers.cloudflare.com/_astro/builds-notifications-slack.rcRiU95L_169ufw.webp)  
For setup instructions, refer to the [template README ↗](https://github.com/cloudflare/templates/tree/main/workers-builds-notifications-template#readme) or the [Event Subscriptions documentation](https://developers.cloudflare.com/queues/event-subscriptions/manage-event-subscriptions/).

Aug 19, 2025
1. ### [Subscribe to events from Cloudflare services with Queues](https://developers.cloudflare.com/changelog/post/2025-08-19-event-subscriptions/)  
[ Queues ](https://developers.cloudflare.com/queues/)  
You can now subscribe to events from other Cloudflare services (for example, [Workers KV](https://developers.cloudflare.com/kv/), [Workers AI](https://developers.cloudflare.com/workers-ai), [Workers](https://developers.cloudflare.com/workers)) and consume those events via [Queues](https://developers.cloudflare.com/queues/), allowing you to build custom workflows, integrations, and logic in response to account activity.  
![Event subscriptions architecture](https://developers.cloudflare.com/_astro/queues-event-subscriptions.3aVidnXJ_Z2p3fRA.webp)  
Event subscriptions allow you to receive messages when events occur across your Cloudflare account. Cloudflare products can publish structured events to a queue, which you can then consume with [Workers](https://developers.cloudflare.com/workers/) or [pull via HTTP from anywhere](https://developers.cloudflare.com/queues/configuration/pull-consumers/).  
To create a subscription, use the dashboard or [Wrangler](https://developers.cloudflare.com/workers/wrangler/commands/queues/#queues-subscription-create):  
Terminal window  
```  
npx wrangler queues subscription create my-queue --source r2 --events bucket.created  
```  
An event is a structured record of something happening in your Cloudflare account – like a Workers AI batch request being queued, a Worker build completing, or an R2 bucket being created. Events follow a consistent structure:  
Example R2 bucket created event  
```  
{  
  "type": "cf.r2.bucket.created",  
  "source": {  
    "type": "r2"  
  },  
  "payload": {  
    "name": "my-bucket",  
    "location": "WNAM"  
  },  
  "metadata": {  
    "accountId": "f9f79265f388666de8122cfb508d7776",  
    "eventTimestamp": "2025-07-28T10:30:00Z"  
  }  
}  
```  
Explain Code  
Current [event sources](https://developers.cloudflare.com/queues/event-subscriptions/events-schemas/) include [R2](https://developers.cloudflare.com/r2/), [Workers KV](https://developers.cloudflare.com/kv/), [Workers AI](https://developers.cloudflare.com/workers-ai/), [Workers Builds](https://developers.cloudflare.com/workers/ci-cd/builds/), [Vectorize](https://developers.cloudflare.com/vectorize/), [Super Slurper](https://developers.cloudflare.com/r2/data-migration/super-slurper/), and [Workflows](https://developers.cloudflare.com/workflows/). More sources and events are on the way.  
For more information on event subscriptions, available events, and how to get started, refer to our [documentation](https://developers.cloudflare.com/queues/event-subscriptions/).

May 09, 2025
1. ### [Publish messages to Queues directly via HTTP](https://developers.cloudflare.com/changelog/post/2025-05-09-publish-to-queues-via-http/)  
[ Queues ](https://developers.cloudflare.com/queues/)  
You can now publish messages to [Cloudflare Queues](https://developers.cloudflare.com/queues/) directly via HTTP from any service or programming language that supports sending HTTP requests. Previously, publishing to queues was only possible from within [Cloudflare Workers](https://developers.cloudflare.com/workers/). You can already consume from queues via Workers or [HTTP pull consumers](https://developers.cloudflare.com/queues/configuration/pull-consumers/), and now publishing is just as flexible.  
Publishing via HTTP requires a [Cloudflare API token](https://developers.cloudflare.com/fundamentals/api/get-started/create-token/) with `Queues Edit` permissions for authentication. Here's a simple example:  
Terminal window  
```  
curl "https://api.cloudflare.com/client/v4/accounts/<account_id>/queues/<queue_id>/messages" \  
  -X POST \  
  -H 'Authorization: Bearer <api_token>' \  
  --data '{ "body": { "greeting": "hello", "timestamp":  "2025-07-24T12:00:00Z"} }'  
```  
You can also use our [SDKs](https://developers.cloudflare.com/fundamentals/api/reference/sdks/) for TypeScript, Python, and Go.  
To get started with HTTP publishing, check out our [step-by-step example](https://developers.cloudflare.com/queues/examples/publish-to-a-queue-via-http/) and the full API documentation in our [API reference](https://developers.cloudflare.com/api/resources/queues/subresources/messages/methods/push/).

Apr 17, 2025
1. ### [Increased limits for Queues pull consumers](https://developers.cloudflare.com/changelog/post/2025-04-17-pull-consumer-limits/)  
[ Queues ](https://developers.cloudflare.com/queues/)  
[Queues pull consumers](https://developers.cloudflare.com/queues/configuration/pull-consumers/) can now pull and acknowledge up to **5,000 messages / second per queue**. Previously, pull consumers were rate limited to 1,200 requests / 5 minutes, aggregated across all queues.  
Pull consumers allow you to consume messages over HTTP from any environment—including outside of [Cloudflare Workers](https://developers.cloudflare.com/workers). They’re also useful when you need fine-grained control over how quickly messages are consumed.  
To setup a new queue with a pull based consumer using [Wrangler](https://developers.cloudflare.com/workers/wrangler/), run:  
Create a queue with a pull based consumer  
```  
npx wrangler queues create my-queue  
npx wrangler queues consumer http add my-queue  
```  
You can also configure a pull consumer using the [REST API](https://developers.cloudflare.com/api/resources/queues/subresources/consumers/methods/create/) or the Queues dashboard.  
Once configured, you can pull messages from the queue using any HTTP client. You'll need a [Cloudflare API Token](https://developers.cloudflare.com/fundamentals/api/get-started/create-token/) with `queues_read` and `queues_write` permissions. For example:  
Pull messages from a queue  
```  
curl "https://api.cloudflare.com/client/v4/accounts/${CF_ACCOUNT_ID}/queues/${QUEUE_ID}/messages/pull" \  
--header "Authorization: Bearer ${API_TOKEN}" \  
--header "Content-Type: application/json" \  
--data '{ "visibility_timeout": 10000, "batch_size": 2 }'  
```  
To learn more about how to acknowledge messages, pull batches at once, and setup multiple consumers, refer to the [pull consumer documentation](https://developers.cloudflare.com/queues/configuration/pull-consumers).  
As always, Queues doesn't charge for data egress. Pull operations continue to be billed at the [existing rate](https://developers.cloudflare.com/queues/platform/pricing), of $0.40 / million operations. The increased limits are available now, on all new and existing queues. If you're new to Queues, [get started with the Cloudflare Queues guide](https://developers.cloudflare.com/queues/get-started).

Mar 27, 2025
1. ### [New Pause & Purge APIs for Queues](https://developers.cloudflare.com/changelog/post/2025-03-25-pause-purge-queues/)  
[ Queues ](https://developers.cloudflare.com/queues/)  
[Queues](https://developers.cloudflare.com/queues/) now supports the ability to pause message delivery and/or purge (delete) messages on a queue. These operations can be useful when:  
   * Your consumer has a bug or downtime, and you want to temporarily stop messages from being processed while you fix the bug  
   * You have pushed invalid messages to a queue due to a code change during development, and you want to clean up the backlog  
   * Your queue has a backlog that is stale and you want to clean it up to allow new messages to be consumed  
To pause a queue using [Wrangler](https://developers.cloudflare.com/workers/wrangler/), run the `pause-delivery` command. Paused queues continue to receive messages. And you can easily unpause a queue using the `resume-delivery` command.  
Pause and resume a queue  
```  
$ wrangler queues pause-delivery my-queue  
Pausing message delivery for queue my-queue.  
Paused message delivery for queue my-queue.  
$ wrangler queues resume-delivery my-queue  
Resuming message delivery for queue my-queue.  
Resumed message delivery for queue my-queue.  
```  
Purging a queue permanently deletes all messages in the queue. Unlike pausing, purging is an irreversible operation:  
Purge a queue  
```  
$ wrangler queues purge my-queue  
✔ This operation will permanently delete all the messages in queue my-queue. Type my-queue to proceed. … my-queue  
Purged queue 'my-queue'  
```  
You can also do these operations using the [Queues REST API](https://developers.cloudflare.com/api/resources/queues/), or the dashboard page for a queue.  
![Pause and purge using the dashboard](https://developers.cloudflare.com/_astro/pause-purge.SQ7B3RCF_2dqU5K.webp)  
This feature is available on all new and existing queues. Head over to the [pause and purge documentation](https://developers.cloudflare.com/queues/configuration/pause-purge) to learn more. And if you haven't used Cloudflare Queues before, [get started with the Cloudflare Queues guide](https://developers.cloudflare.com/queues/get-started).

Feb 14, 2025
1. ### [Customize queue message retention periods](https://developers.cloudflare.com/changelog/post/2025-02-14-customize-queue-retention-period/)  
[ Queues ](https://developers.cloudflare.com/queues/)  
You can now customize a queue's message retention period, from a minimum of 60 seconds to a maximum of 14 days. Previously, it was fixed to the default of 4 days.  
![Customize a queue's message retention period](https://developers.cloudflare.com/_astro/customize-retention-period.CpK7s10q_19dmJh.webp)  
You can customize the retention period on the settings page for your queue, or using Wrangler:  
Update message retention period  
```  
$ wrangler queues update my-queue --message-retention-period-secs 600  
```  
This feature is available on all new and existing queues. If you haven't used Cloudflare Queues before, [get started with the Cloudflare Queues guide](https://developers.cloudflare.com/queues/get-started).

[Search all changelog entries](https://developers.cloudflare.com/search/?contentType=Changelog+entry)