Roughly one delivery in two hundred fires twice with the same event id. We have made our side idempotent so nothing is broken, but we found out the hard way.
2 Replies
Ada WhitfieldJul 9
You should not have had to find that out the hard way, and our documentation should have said at-least-once rather than implying exactly-once. Both parts are being fixed.
Ada WhitfieldJul 20
Done. Duplicates are suppressed for 24 hours on the event id, which removes almost all of them, and the docs now say plainly that delivery is at-least-once and that you should key on the event id. Building idempotently was the right call and stays the right call.