Duplicates

Duplicates Overview

• When duplicates are found they are added to the Duplicates/Pending duplicates table.
• Duplicates can be added as Pending (manual review) or completed automatically if rules and connection support automatic merges.

Duplicate Actions

Understanding what happens to duplicates in different states helps you manage your deduplication workflow effectively.

Pending

When a duplicate is waiting for your review, it stays in “Pending” status. If the same pair of records is detected again in a later job (same IDs), DeDuplica will update the duplicate details (like the probability score and merge data) but keep the original execution ID. This means you won’t see multiple pending duplicates for the same pair—just one that gets updated with the latest information.

Completed

When you complete a duplicate, the action you’ve configured happens:

• Automatic merge (if your connection supports it)
• Webhook triggered to notify other systems

Once a duplicate is completed, it’s locked in for your records. If a future job finds the same pair again, DeDuplica will create a fresh duplicate record—because your data may have changed and it might be worth reviewing again.

Cancelled

This means you’ve decided these aren’t really duplicates. Maybe they looked similar but turned out to be different records.

When the next job runs:

• If it finds the exact same pair with the same values and probability, it won’t create a new duplicate (we trust your judgment).
• If it finds the same IDs but the values have changed, it will create a new duplicate for you to review—because something changed and it might be worth a second look.

Locked

Locking a duplicate freezes those two specific record IDs permanently. This tells DeDuplica: “These two records should never be considered duplicates again.”

Even if the data in those records changes completely in future jobs, DeDuplica will not flag them as duplicates—the lock stays in place. This is useful when you know two records look similar but should always remain separate.

The only way to allow them to be detected as duplicates again is to delete the locked duplicate record.

Deleted

Sometimes things go wrong, or you want to clear out a mistake. Deleting a duplicate removes it from your list.

DeDuplica treats it like it never existed. If a future job finds the same pair again, it will create a fresh duplicate record just like the first time.