Hi, I've quickly implemented a queue in front of a (prod) worker that takes some time to finish. It

Hi,
I've quickly implemented a queue in front of a (prod) worker that takes some time to finish. It was previously called via a webhook (which I do not control) but the caller times out before the worker can finish. The webhook does retry which duplicates data flow. Do you guys recommend a different approach (also because queues is still in beta)?

GGerbuuun Hi, I've quickly implemented a queue in front of a (prod) worker that takes some...

Hello, I’m Allie!•5/8/24, 8:35 PM

You can also use

waitUntil

waitUntil

to process the Webhook, then return a Response back basically instantly

GerbuuunOP•5/8/24, 8:41 PM

I'm doing some browser rendering stuff. With

waitUntil

waitUntil

it basically returns a response first and then starts the rendering?

Conner•5/8/24, 8:42 PM

"Attempts" on queues is a bit confusing

Conner•5/8/24, 8:43 PM

Anyone know if it starts at 0 or 1 for first execution?

Conner•5/8/24, 8:43 PM

So if my my max_retries is 3, will attempts be 0,1,2, or 1,2,3?

Conner•5/8/24, 8:44 PM

Would be nice if this were explicit in docs too, @HardlyWorkin'

GGerbuuun I'm doing some browser rendering stuff. With `waitUntil` it basically returns a ...

Hello, I’m Allie!•5/8/24, 8:52 PM

Sort of. You do something like this:

ctx.waitUntil(someWorkFunction(data));
return new Response();

ctx.waitUntil(someWorkFunction(data));
return new Response();

CConner Would be nice if this were explicit in docs too, @HardlyWorkin'

Hello, I’m Allie!•5/8/24, 8:53 PM

It starts at 1

HHello, I’m Allie!Sort of. You do something like this: ```ts ctx.waitUntil(someWorkFunction(data))...

GerbuuunOP•5/8/24, 9:42 PM

Thanks for the tip!

Rabid•5/9/24, 4:50 PM

As soon as I add bindings for a queue producer, my scheduled cron stops working:

[[queues.producers]]
 queue = "wow-cataclysm-auctions-queue"
 binding = "QUEUE"

[[queues.producers]]
 queue = "wow-cataclysm-auctions-queue"
 binding = "QUEUE"

Rabid•5/9/24, 4:50 PM

If I remove that from my wrangler.toml, my schedule cron worker works again

Rabid•5/9/24, 4:56 PM

My producer code right now is literally just

export default {
  async scheduled(controller, env, ctx) {
    console.log('test')

  }
}

export default {
  async scheduled(controller, env, ctx) {
    console.log('test')

  }
}

Rabid•5/9/24, 4:57 PM

And the console.log doesn't fire if that queue binding exists

Rabid•5/9/24, 5:05 PM

In fact it has nothing to do with schedule, even just following the default instructions here: https://developers.cloudflare.com/queues/get-started/ results in a hello world fetch handler returning 500

Cloudflare Docs

Get started · Cloudflare Queues

Cloudflare Queues is a flexible messaging queue that allows you to queue messages for asynchronous processing. By following this guide, you will …

Rabid•5/9/24, 5:05 PM

If you remove the binding, the fetch handler works again

kian•5/9/24, 5:07 PM

Deployed, or with

wrangler dev

wrangler dev

Deep•5/9/24, 8:33 PM

[[queues.consumers]]
queue = "send-url-test"
max_batch_size = 10
max_batch_timeout = 2

i am using these configuration of my queue, the batch_size limit is working, but the timeout limit is not working,

DDeep [[queues.consumers]] queue = "send-url-test" max_batch_size = 10 max_batch...

Matt Silverlock•5/9/24, 11:47 PM

What do you mean by “not working” - ?

DDeep [[queues.consumers]] queue = "send-url-test" max_batch_size = 10 max_batch...

Matt Silverlock•5/9/24, 11:47 PM

If it hits 10 messages OR 2 seconds, the messages will be flushed to the consumer. Whichever occurs first.

DDeep [[queues.consumers]] queue = "send-url-test" max_batch_size = 10 max_batch...

Matt Silverlock•5/9/24, 11:47 PM

https://developers.cloudflare.com/queues/configuration/batching-retries/#batching

Cloudflare Docs

Batching, Retries and Delays · Cloudflare Queues

When configuring a consumer Worker for a queue, you can also define how messages are batched as they are delivered.

MMatt Silverlock https://developers.cloudflare.com/queues/configuration/batching-retries/#batchin...

Deep•5/10/24, 4:12 AM

yup you are right, but my queue stops sending messages after the first batch id delivered and acknowledged

Dawson•5/11/24, 1:52 PM

Would this be a good use case for stripe billing? I need to charge the user per request

Dawson•5/11/24, 1:52 PM

I will pretty easily exceed the 100 operations a second rate limiting that Stripe applies. I could also scan through the db every 10 mins or so and bill them that way

johtso•5/11/24, 8:41 PM

if I disable concurrency, is there still a chance of a message being delivered more than once?

johtso•5/11/24, 8:43 PM

I have a usecase where I'm interacting with an external service that makes it very hard to achieve idempotency (it's only possible to check if an email has already been sent after waiting about a minute for it to be "indexed")

johtso•5/11/24, 8:44 PM

so if there's an error I need to make sure not to reattempt the job until a certain amount of time has elapsed

johtso•5/11/24, 8:44 PM

otherwise I risk sending users duplicate emails

LordSilver•5/12/24, 9:18 AM

you have no info from the dashboard that a queue is a DLQ of another queue?

LordSilver•5/12/24, 9:22 AM

how can you see event notification in your dashboard? https://developers.cloudflare.com/r2/buckets/event-notifications/

Cloudflare Docs

Event notifications · Cloudflare R2 docs

Event notifications send messages to your queue when data in your R2 bucket changes. You can consume these messages with a consumer Worker or pull …

LordSilver•5/12/24, 9:22 AM

after you created it

LordSilver•5/12/24, 9:23 AM

I went to check on the R2 bucket and also on the queue, but cannot see which triggers are configured

LordSilver•5/12/24, 9:23 AM

or maybe this is completely missing from the dashboard at the moment?

Deep•5/13/24, 5:20 PM

I have a question, what happens when one batch is procesing by the consumer worker, and the next batch is also full in the queue, and we are still adding the messages in queue?

Unsmart•5/13/24, 5:52 PM

Im a bit confused by the question, the messages would still be added to the queue and get processed eventually

LordSilver•5/14/24, 2:32 PM

what's the command to list all event notifications for a given r2 bucket?

UUnsmart Im a bit confused by the question, the messages would still be added to the queu...

Deep•5/15/24, 2:58 AM

so if the comsumer workers are not free where do the queue send the next batch to?

DDeep so if the comsumer workers are not free where do the queue send the next batch t...

Unsmart•5/15/24, 3:34 AM

No where it stays in the queue. Think of queues like waiting in line for a cashier... if a cashier is open you can go to checkout, if not you just wait until one is open

UUnsmart No where it stays in the queue. Think of queues like waiting in line for a cashi...

Deep•5/15/24, 4:18 PM

thank you for clearing , so what i understand is
"a queue can have a large number of messages in waiting state in backlog,
and when the consumers are free it sends BATCH_SIZE number of messages in bulk everytime"

so just one more question i am using browser rendering in the crawler and it has a limit of 2 new browsers per minute per account, so if that limit gives an error should I add retry delay in the queue? and if I give msg.retry() for one message from a batch, will the queue send only this message or send another batch including this message?

Deep•5/15/24, 4:37 PM

Also I launch a browser session with { keep_alive : 600000 }, so it should stay alive for 10 minutes, I am not doing browser.close() too, instead i am doing browser.disconnect(), then why it is getting released after 60 seconds of inactivity

Paul•5/15/24, 9:56 PM

So my understanding is that a queue can only have a single consumer. How would we handle a 1 to many situation? Let’s say I fire an event when a user signs up, so I place a “UserSignedUp” event on the queue. Now I’d like to have a bunch of consumers that are decoupled and can react to that event (notifying, saving to database, etc). They all do incredibly important operations, so I need a guaranteed delivery to each consumer. Is this possible in Cloudflare Queues?

Paul•5/15/24, 10:26 PM

I’m also seeing Pub/Sub is offered but without >= “at least once” guarantees.

PPaul So my understanding is that a queue can only have a single consumer. How would w...

Matt Silverlock•5/16/24, 12:00 AM

Queues guarantees delivery, but with at least once, so in some cases a message may be delivered more than once: https://developers.cloudflare.com/queues/reference/delivery-guarantees/

Cloudflare Docs

Delivery guarantees · Cloudflare Queues

Delivery guarantees define how strongly a messaging system enforces the delivery of messages it processes.

MMatt Silverlock Queues guarantees delivery, but with at least once, so in some cases a message m...

Paul•5/16/24, 12:01 AM

But with most other queue based systems, there can be many consumers per queue..

Paul•5/16/24, 12:01 AM

Which enables a nice decoupled event driven system

PPaul But with most other queue based systems, there can be many consumers per queue..

Matt Silverlock•5/16/24, 12:02 AM

Yes, but how are you decoupling each consumer here? Multiple consumers are still going to receive the same events — what it sounds like you want it a way to batch based on a key (defining an event type)

Paul•5/16/24, 12:02 AM

The only other way I can think to do it is have the main consumer as a “dispatch” and have it send the event back out on a bunch of other queues, but this sounds terrible

MMatt Silverlock Yes, but how are you decoupling each consumer here? Multiple consumers are still...

Paul•5/16/24, 12:03 AM

I’m looking for essentially pub/sub but with at least once guarantee

PPaul I’m looking for essentially pub/sub but with at least once guarantee

Matt Silverlock•5/16/24, 12:05 AM

Can you describe more here? A Pub/Sub consumer is going to pull something off the topic, but it’s all the same set of messages. I don’t see how this is any more decoupled: a single “UserSignedUp” event is still going to a single consumer.

Hi, I've quickly implemented a queue in front of a (prod) worker that takes some time to finish. It

Similar Threads

Similar Threads

Similar Threads