# Safe API retry checklist
- Treat client timeouts as unknown remote outcomes, not rollbacks.
- Reuse one idempotency key per logical operation.
- Scope deduplication to tenant and request fingerprint.
- Claim operations atomically across workers.
- Limit retries with deadlines, jitter and error classification.
- Persist or reconcile terminal outcomes and test crash boundaries.
- Do not retry authorization or deterministic validation errors.

Sources:
https://aws.amazon.com/builders-library/timeouts-retries-and-backoff-with-jitter/
https://www.postgresql.org/docs/current/ddl-constraints.html