Short answer: use FIFO deduplication for a five-minute duplicate window, then enforce an application idempotency key in your database or cache; exactly-once delivery is not a safe assumption. For many media workloads, a standard at-least-once queue with an idempotent worker is the simpler rate-limited jobs design.
The page usually arrives late. A worker pool is draining slowly, the provider starts returning 429, and the queue depth alert fires after the deadline has already slipped. Then a retry lands beside its original message. The on-call sees two thumbnails being rendered for one upload and has to decide which side effect to keep.
I start from that alert because it exposes the real contract: a queue controls delivery, while the consumer owns correctness. FIFO can suppress a duplicate message for five minutes.…