Skip to main content

Idempotency Center

The Idempotency Center shows which event types are protected by an idempotency key, the safeguard that stops a re-delivered or replayed event from running its side effects twice.

What you'll see​

  • Summary stats: how many event types are keyed, how many duplicate groups have been seen, how many duplicates were blocked, how many event types are currently safe to reprocess, and when the last duplicate was caught.
  • A replay safety matrix: one row per event type, with a sample key, when it was last seen, how many duplicates it caught, and a verdict: safe to reprocess, or not yet protected.

Why it matters​

Before you rely on a retry, or before Replay ships, this page is how you confirm an event type won't cause duplicate side effects (like double-charging a customer or sending the same notification twice) if it gets processed more than once. See Idempotency in Core Concepts for the underlying idea, and the Python SDK idempotency guide if you want to add keying to more of your event types.