Reliability
Idempotency
Idempotency is the property that running the same step twice has the same effect as running it once, so a retry never creates a duplicate record or payment.
How it works in practice
Integrations retry. Webhooks are delivered more than once, networks time out after the other side has already acted, and people press the button twice. If the step that creates an invoice is not idempotent, each retry creates another invoice.
The usual techniques are an idempotency key sent with each request, which APIs such as Stripe support, an upsert that writes by a unique key, and a check for an existing record before creating one. We treat idempotency as a requirement for any step that writes money, stock or customer-facing messages.
A worked example
A webhook from the payment provider arrives twice for the same payment. The workflow upserts by payment ID, so the second delivery updates the same record and the customer gets one receipt.
Examples in this glossary describe typical builds for companies of 1 to 1,000 people. They are not named client results.















