Idempotency keys and safe re-runs
- What it is
- Every incoming request or scheduled result carries a key that identifies it. The key is checked before anything is written, and summary rows are written with an upsert on a fixed key.
- Why it matters
- People double-click, browsers retry and schedules overlap. Without a key, each of those becomes a duplicate ticket, payment or alert. With one, running the same thing twice is harmless.
- How we apply it
- We decide the key for every write before we build the step that makes it, and test each workflow by sending the same request twice.
- Where it appears