Power Automate Needs Idempotency
Retries and duplicate triggers are normal; flows must prevent the same business action from happening twice.
Cloud automation behaves as at-least-once delivery in more places than makers expect. Triggers repeat, users resubmit and retries follow ambiguous timeouts where the first request may already have succeeded.
Assign a stable business operation key and record completion in a durable store. Check before sending payments, creating orders or issuing communications. Use destination-system idempotency capabilities where available.
Do not rely on “Get items, then create” without concurrency protection; two runs can pass the check together. Use alternate keys, atomic operations or controlled concurrency.
Idempotency is not advanced optimisation. It is what separates safe recovery from charging a customer twice after a timeout.