Check a Queue for Message Loss
Added 2026-11-04
Acks, retries and visibility timeouts are where messages disappear.
Here is a queue consumer. Check: 1) when it can lose a message — acking too early, crashing, timeout; 2) whether duplicate delivery is safe; 3) whether visibility timeout or retry interval can make messages reappear or become stuck; 4) whether a dead-letter queue is needed; 5) give a minimal reliable consumer flow; 6) point out the least obvious loss risk.
Site original
Chinese original
How to use
丢消息往往不是队列的问题，是确认的时机不对。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.