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)
5 Replies
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
what I do is if the
queue.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.send would never fail (performing any needed retries behind the scenes) unless somehow the calling worker isolate lost all network/disk access completelySo 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
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
@Sid do you think it's specific to my Queue ID? Would it help if I just recreated the queue?
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.