I've seen this intermittently as well, I

I've seen this intermittently as well, I don't think it necessarily always corresponds exactly to how fast you are sending, but rather the current state of the queue backend (if the machine/isolate itself is failing-over/overloaded for other reasons)

welz•9/25/25, 8:33 PM

What is the recommended solution in these circumstances? I've never got this error until today and got it already a few times - my guess is something changed

John SpurlockOP•9/25/25, 8:39 PM

what I do is if the queue.sendqueue.send fails with these and other sorts of errors (after a few retry-with-backoff attempts in-isolate), I try to quickly save the message to a DO, then replay later

in a perfect world, queue.sendqueue.send would never fail (performing any needed retries behind the scenes) unless somehow the calling worker isolate lost all network/disk access completely

Sid•9/25/25, 8:41 PM

So I see the 429s and have a theory for what’s going on, but this is very likely transient. I will still try and set up a trap to see if I can get more details

welz•9/25/25, 8:42 PM

I'll try adding a failsafe like John suggested to my code - but yes in a perfect world that's how we'd hope queue.send would behave

welz•9/25/25, 8:58 PM

@Sid do you think it's specific to my Queue ID? Would it help if I just recreated the queue?

Sid•9/25/25, 9:03 PM

Nah it’s got to do with the DO that backs your queue. Most likely recreating your queue will lead you on the same-ish DO because of where your traffic is coming from.

I've seen this intermittently as well, I

Similar Threads

Similar Threads

Similar Threads