When an iFlow fails midway through a batch, retrying the full payload can duplicate successful records. This discussion shares a practical pattern using idempotency keys, persisted checkpoints, and selective replay so recovery stays safe and observable. What approaches have worked best in your production landscapes?