The Code Pattern That Keeps Our Integrations Stable in Production

When you connect real systems - ERPs, APIs, AI workflows - things don’t behave cleanly. Requests retry. Webhooks get sent twice. Sometimes something succeeds, but you don’t get the response. And then you see it: duplicate orders repeated emails workflows triggering twice This is normal in production. The pattern that keeps this under control is idempotency. The rule Every action should be safe to run more than once. Same input → same result. If the same request hits your system twice, nothing sh