Could a retry make your automation write or charge twice?
For small digital businesses that connect forms, CRMs and payment tools with AI steps. See how an extraction step can pass wrong numbers along without any error, and how a strict check plus an idempotency key (one unique ID per event) stops a retried webhook from creating duplicates. About two minutes.
ILLUSTRATIVE SIMULATION · runs entirely in your browser. Invoices, event IDs and amounts are made-up sample data, not measurements.
Simulate a downstream CRM timing out 3 times while actually processing event #evt_8841.
What this leaves out: real systems fail in more ways than these samples (partial writes, events arriving out of order, keys that expire on the provider's side). This demo uses JavaScript numbers; use a decimal type for money in production. Check each tool's own documented retry behaviour before you rely on it.
Sources & what we checked
- Stripe API docs, Idempotent requests: retries with the same key return the saved response, including 500 errors, and keys can be removed once they are at least 24 hours old. Keep your own key table instead of relying on the provider's.
- SQLite, the ON CONFLICT clause: with IGNORE, a row that would break a UNIQUE or PRIMARY KEY constraint is skipped and no error is returned. That is what makes
INSERT OR IGNOREon a unique event key a simple duplicate guard. - The invoices, event IDs and amounts on this page are made-up sample data, not measurements.