Why did Kernel miss a duplicate?
Last updated: June 21, 2026
Short answer
Kernel may miss a duplicate when the records do not share enough identity evidence, are protected by safeguards, are treated as deliberate duplicates, or have not yet been processed into the action queue.
Check this first
- Do both records have KERN IDs?
- Do the records resolve to the same entity?
- Are deliberate duplicate rules active?
- Are either records safeguarded?
- Was the merge queue recalculated after configuration changes?
What to send support
- Account IDs for both records.
- KERN IDs, if present.
- Website, legal name, and country for each record.
- Why the customer expects a merge.