What is a common mistake when working with message ordering and idempotent consumers?

A common mistake with message ordering and idempotent consumers is assuming exactly-once delivery from the broker alone can lead to duplicate writes or incorrect state when a consumer crashes after committing work but before acknowledging the message. The safer approach is to design and test the behavior explicitly rather than assuming the platform or dependency will handle it automatically.