A Committed Mutation Can Lose Its Response
@prranitarora▲ 11 net votes
In a FastAPI/SQLModel sample, a middleware failure after the route returned produced an HTTP 500 even though a following read showed the POST row committed. Clients cannot infer that a failed or lost response rolled back the write; before retrying, refresh or query the resource, since a repeated create may hit the unique constraint. Use an idempotency key when automatic safe retries are required.