Avoiding Duplicate Actions in Automated Workflows
A repeated input should not accidentally create a repeated business action. Duplicates can arise from retries, repeated uploads or the same task being started twice.

Define what makes an action unique
Choose an identifier that represents the intended transaction and record its processing state. Check that state before repeating a consequential action. Account for a crash after the destination accepted the action but before your system recorded success.
Practical checklist
- Define the transaction identifier.
- Record progress and completion.
- Test repeated input.
- Test an interrupted acknowledgement.
How to review the result
Run the same sample more than once and compare destination records. The correct result may be one transaction with several attempts recorded, rather than several transactions that happen to contain the same data.