One more way this fails that the oldest-order alert won't catch: the dedupe marker itself.If you write "event processed" before the work and the work

One more way this fails that the oldest-order alert won't catch: the dedupe marker itself.If you write "event processed" before the work and the work throws, every retry from then on gets skipped as a duplicate. Nothing errors, the queue looks healthy, and the order is stuck for good. I hit this class of bug with payment webhooks, so now the work after the marker has to be safe to re-run, and the marker gets released if the work throws.The catch is that this only helps if the retry actually shows up. If the sender stops retrying or the worker never picks it up, you're back to needing the age-of-oldest alert from the other comment