Hey folks, I am trying to do some processing on queues, surprisingly they timeout after 60s inside t

Hey folks, I am trying to do some processing on queues, surprisingly they timeout after 60s inside the consumer. On the paid plan, currently testing locally. Any thoughts? It just stops processing no error, nothing.
16 Replies
toadfans
toadfans2mo ago
hello, is queue down now?
{

"name": "Error",
"message": "Queue send failed: Internal Server Error",
"stack": "Error: Queue send failed: Internal Server Error\n at async Object.mutation (bundledWorker-0.9232964110947641.mjs:9562:3)\n at async Object.handler (bundledWorker-0.9232964110947641.mjs:28094:17)\n at async o (bundledWorker-0.9232964110947641.mjs:4128:13)\n at async r (bundledWorker-0.9232964110947641.mjs:4210:92)\n at async o (bundledWorker-0.9232964110947641.mjs:4128:13)\n at async Object.handler (bundledWorker-0.9232964110947641.mjs:14535:28)\n at async o (bundledWorker-0.9232964110947641.mjs:4128:13)\n at async r (bundledWorker-0.9232964110947641.mjs:4210:92)\n at async o (bundledWorker-0.9232964110947641.mjs:4128:13)\n at async Object.handler (bundledWorker-0.9232964110947641.mjs:8361:42)"
}
{

"name": "Error",
"message": "Queue send failed: Internal Server Error",
"stack": "Error: Queue send failed: Internal Server Error\n at async Object.mutation (bundledWorker-0.9232964110947641.mjs:9562:3)\n at async Object.handler (bundledWorker-0.9232964110947641.mjs:28094:17)\n at async o (bundledWorker-0.9232964110947641.mjs:4128:13)\n at async r (bundledWorker-0.9232964110947641.mjs:4210:92)\n at async o (bundledWorker-0.9232964110947641.mjs:4128:13)\n at async Object.handler (bundledWorker-0.9232964110947641.mjs:14535:28)\n at async o (bundledWorker-0.9232964110947641.mjs:4128:13)\n at async r (bundledWorker-0.9232964110947641.mjs:4210:92)\n at async o (bundledWorker-0.9232964110947641.mjs:4128:13)\n at async Object.handler (bundledWorker-0.9232964110947641.mjs:8361:42)"
}
requestId: 8cfd3fdf8f3984b7
Lance
Lance2mo ago
Hi, anyone encounters similar issue that queue's backlog just grows and no message is delivered to worker handler? Nothing changed from code side. It just suddenly happened a few hours ago.
No description
Unknown User
Unknown User2mo ago
Message Not Public
Sign In & Join Server To View
Sam
Sam2mo ago
Any update on when queues are coming to remote mode https://github.com/cloudflare/workerd/issues/855 or is it possible to run queues locally and my other bindings remotely?
GitHub
🐛 BUG: wrangler dev --remote fails with Error 1104, Script not fo...
What version of Wrangler are you using? 2.6.2 What operating system are you using? Windows Describe the Bug Add a queue binding in your wrangler.toml, in my case: [[queues.producers]] queue = &quot...
ac
ac2mo ago
Hi, I am having issues using a Pages deployment as a queue producer. It doesn't throw any error, and the service binding for the Queue is there for the Pages app, but the queue never gets a message even though the enqueueing code is definitely getting called. I did notice that on the queue, the "Producer" shows a production and a preview deployment but they just have a generic pages-worker-###-production format and aren't using the name of my Pages app
Unknown User
Unknown User2mo ago
Message Not Public
Sign In & Join Server To View
dangoldin
dangoldin5w ago
Hopefully a quick question - I'm doing some local dev and wanted to confirm my queues are set up properly but I don't see anything queue related in the .wrangler/state/v3/ path (it has cache and d1). Should there be anything created there? I have a Remix app that's published to a queue and then a separate worker to consume so trying to figure out why the worker isn't seeing the messages being published
Unknown User
Unknown User5w ago
Message Not Public
Sign In & Join Server To View
John Spurlock
John Spurlock5w ago
+1, even a notion like sqs's message-group-id as a scaling worker consumer hint, not for fifo (since cf doesn't do fifo)
Pranshu Maheshwari
thanks for the feedback here! very detailed & agreed that this is a pain point with queues today 🙂 we're thinking about ways to improve this. our plan right now is to add the ability to connect multiple consumers to a single queue. you'll be able to specify partition keys to route specific messages to specific consumers. and ideally this can be dynamic, so you don't have to specify all the rules ahead of time. this project is still in the design phase though, so it's too soon to share timelines. dynamically creating queues doesn't work well today, alas! rather than 1 queue per user, would you be able to setup a few queues as high-priority queues, and setup separate low priority queues? by default, messages get routed to the high priority queues. if a user uploads 10k files at once, you route those messages to the low priority queues so that they don't block each other?
Brett Willis
Brett Willis5w ago
Any plans to support pushing to Queues from an external platform direct via the rest API (not via an intermediate Worker)?
Pranshu Maheshwari
We published a deep dive on the Queues architecture today! https://blog.cloudflare.com/how-we-built-cloudflare-queues/
The Cloudflare Blog
Durable Objects aren't just durable, they're fast: a 10x speedup fo...
Learn how we built Cloudflare Queues using our own Developer Platform and how it evolved to a geographically-distributed, horizontally-scalable architecture built on Durable Objects. Our new architecture supports over 10x more throughput and over 3x lower latency compared to the previous version.
Saqib (Langbase)
Saqib (Langbase)OP4w ago
I have a queue with batch of size 50 and timeout of 10s. Few questions: 1- If I do .send will msg be processed as soon as it arrives or it will wait for 10s before processing? 2- If a batch of 50 msgs is being processed by consumer and it takes longer than 10s, what happens next, if there are more messages waiting to be processed. 2.1- Will a new batch be delivered to the consumer? If so, will it make a new instance of the consumer or same isntance of consumer will process it. 2.2 Will new batch wait till the processing of previous batch is complete? 3- There is something related to concurrency. But it seems like it is never triggered. How can I verify if it is being triggered? For now it seems like all processing is sequential. It becomes a bottleneck very quickly if mutliple users are using it.
Unknown User
Unknown User4w ago
Message Not Public
Sign In & Join Server To View
ajgeiss0702
ajgeiss07024w ago
messages in my queue, even if they dont have a delay attached to them, are often not being delivered until 20-30 minutes after they are queues (sometimes more, the most ive seen so far is 1h 20m). any idea why that might be? and ones that do have a delay attached to them are 20-30 minutes later than they are supposed to be it looks like it started happening on october 23rd, around 9pm UTC
ueryooo
ueryooo4w ago
Can R2 Event Notifications to Queue be tested in local development?
Want results from more Discord servers?
Add your server