Hi! I deleted a bunch of R2 bucket notifications & buckets but I can not delete the queue that was r
Hi! I deleted a bunch of R2 bucket notifications & buckets but I can not delete the queue that was referenced. I always receive the error "cannot delete queue bucketav-rhyglnin that serves as a target for event notifications". I have no buckets left so this is likely not the case. Are there any reqasons for that? Is there something happening in the background before I can delete the queue? If I look at the queue in the dashboard it says "This queue does not have a consumer". Clicking the delete button in the UI is broken as well. I can see the error in the browser logs but not the UI.
17 Replies
hmm, it seems like my messages are being retried immediately after an implicit retry instead of waiting the configured 60 seconds..
What would be the benefits of having a producer and consumer in two different workers? Or vice versa?
Queue "consumer concurrency" feature does not seem to be suitable for scenarios that rely on sequential execution.
Hey all, does anybody if there is a way to get both Queues & the Browser Rendering API working nicely together in local dev? Seems Queues doesn't support --remote but Browser Rendering only works when using --remote?
Did not have your problem, but you could try to just put your queue script inside the fetch() one to test it out remotely.
Thanks. I think we’re switching to scheduled instead. Our use case didn’t have massive throughput. Cheers for quick reply
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
Can you expan a bit more on this? Is the consumer queue not picking it up? Can you also share your wrangler.toml config for the queues?
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
hey! is there any (inofficial) goal for queues performance? will it ever be comparable to eg sqs? sending to the queue is currently multiiple 100ms, and it takes multiple seconds for a worker to receive it. and throughput is much much lower at the moment.
I haven't run into messages dropping or batches dropping. I have built some interesting architecture where I have a message-producer API which abstracts all the applications from needing to know about how to send messages. We used a KV bound to the message producer API to know what queue to route to and bind the worker to any queue. I know there are limits to the binding, but this API has made it easy to onboard queues for a few different use cases. I'm ready for this to move to GA. What issues is the team waiting on solving before moving it to GA?
Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
is there a plan to have messages be "grouped" and sent that way? i have a merchantId prop on my messages and i want to handle up to 20 messages per merchant, but there isn't really a way to do that right now
it would be really neat if i could do that honestly
Hi there, just wanted to know if there is any way to see which buckets are sending notifications to a queue
Couple queries:
Any plans to add a
Message.deadletter
method? I have some use cases where I know the message will always fail and it needs manual triage.
It'd be great to have redrive functionality to move messages from the deadletters to processing queue once any issues with the deadletters have been resolved (e.g. temp outage). AWS SQS has similar functionality https://docs.aws.amazon.com/AWSSimpleQueueService/latest/SQSDeveloperGuide/sqs-configure-dead-letter-queue-redrive.htmlLearn how to configure a dead-letter queue redrive in Amazon SQS - ...
Learn how to configure an Amazon SQS dead-letter queue redrive to move messages from a dead-letter queue to a source queue or other standard queue.
Also, are there plans to suppport passing a
Message
into an RPC Worker?I don't see wrangler.toml's equivalent of
[[queues.consumers]]
referenced in https://developers.cloudflare.com/workers/configuration/multipart-upload-metadata/#bindings -- is that intentional? if so, how does one configure a Worker uploaded from the API to be a queue consumer? I've added "type": "queue"
in my bindings metadata, but that only seems to register the worker as a queue producer