Fix/max retries deadletter queue#963
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Lower the default AWARENESS_MAX_ATTEMPTS from 8 to 3.
A dead-lettered delivery was left with status 'failed', which claimBatch selects - so the engine re-claimed it every tick, re-attempted it, inflated its attempt count without bound and inserted a fresh dead-letter row each time. Mark exhausted deliveries with a terminal 'dead' status and exclude any delivery at/over the attempt cap from claiming.
Description of change
Issue Number
Type of change
How the change has been tested
Change checklist