hmm, it seems like my messages are being
hmm, it seems like my messages are being retried immediately after an implicit retry instead of waiting the configured 60 seconds..
3 Replies
id: 46ff84346aa373686c92055cc6259252
2024-09-05T15:02:09.183Z
@Pranshu Maheshwari any chance of getting some eyes on this when you have a moment? 🙏
I'm relying on the queue configuration to stop me spamming my APIs if there are failures
Retry delay seems to be ignored for some reason
hey, thanks for the ping, I totally missed this
you probably checked this already, but just in case: when marking a message to be retried, you're not setting
delaySeconds
on the individual message right?
also, is this happening locally or when you deploy your consumer? there's a known issue with local consumers & retry delays (which is expected to be fixed by next week)I was just looking into this, and can't seem to repro during local dev or after deployment, interestingly
My Worker is really simple:
wrangler.toml:
Can you try logging the
message.attempts
to make sure you don't have similar-looking messages?
Also message.timestamp
might also help
Tried individual message.retry
s as well, that also seems to work as expected