Skip to main content

Stable key rule

Reuse the same idempotency key for every retry of the same logical mutation. A fresh key represents new work and can create a duplicate.

Unconfirmed mutations

If the connection drops after sending a mutation:
  1. Keep the original key.
  2. Read the known run or resource if an identifier was returned.
  3. Retry the same payload with the same key when the contract permits.
  4. Treat a digest mismatch as a reconciliation failure, not a signal to bypass it.
Last modified on August 14, 2026