Idempotency Keys Everywhere
Give every flow idempotency keys derived from stable business identifiers so reruns produce the same result without duplicates. Store response fingerprints, version numbers, and timestamps. If a webhook retries three times, the system should still produce exactly one invoice, one task list, and one acknowledgement, protecting both revenue and credibility.