Duplicate Records After an Integration
A sync can move every expected record and still be wrong if the destination contains unintended duplicates.
Duplicates are a data correctness problem
Retries, repeated requests, or destination behavior can create multiple copies of the same logical record.
Define the unique business key
Use the identifier that should represent one logical record, such as an order ID or invoice number.
Verify the final destination state
Post-sync reconciliation checks what actually exists after the workflow finishes.
Frequently asked questions
How do I detect duplicate records after a sync?
Group destination records by the identifier that should be unique and surface identifiers that occur more times than expected.
Do not stop at integration success.
Compare the actual source and target data after the workflow finishes.
Start verifying→