Duplicate Error Logs
Duplicate Error Logs is a Setup page that records instances where Duplicate Rules blocked or flagged record creation or updates.
Definition
Duplicate Error Logs is a Setup page that records instances where Duplicate Rules blocked or flagged record creation or updates. It provides details about the duplicate rule that fired, the matching records identified, and the action taken (block or alert), helping administrators monitor and fine-tune their duplicate management strategy.
In plain English
“Here's a simple way to think about it: Duplicate Error Logs is the audit trail for your duplicate rules. Every time a rule blocks or alerts on a near-duplicate, the event is captured here - telling you whether the rules catch real duplicates or just produce friction.”
Worked example
After implementing a new Duplicate Rule on Leads, the admin at Summit Retail checks Duplicate Error Logs and discovers that 200 leads were blocked in the past week. She reviews the blocked entries and finds that 180 were genuine duplicates but 20 were false positives caused by overly strict matching criteria. She adjusts the matching rule to reduce false positives.
Why Duplicate Error Logs tell you whether your duplicate rules are actually working
Setting up Duplicate Rules is straightforward; verifying that they're firing as intended is harder. Duplicate Error Logs is the page that closes the loop. Every time a rule blocks a record creation or alerts on a near-duplicate, it lands here - with the rule name, the matching records, the user who triggered it, and the action taken. For an admin tuning duplicate management, this log is the empirical record of whether the rules match real duplicates or just produce friction.
The reason it deserves a recurring review is that duplicate rules drift. New record patterns, slight naming conventions, integration loads that bypass the rules entirely - all of these change what "duplicate" looks like, and the rules don't update themselves. Skim this log monthly: rules with zero hits in 90 days are candidates for retirement, and rules with thousands of hits are candidates for a closer look at why so many duplicates are reaching the rule layer in the first place.
How to set up Duplicate Error Logs
Duplicate Error Logs is the page showing recent Duplicate Rule violations — when a Block-action duplicate rule prevented a save, the error is logged here. Useful for debugging "why did this insert fail" issues with bulk integrations.
- Open Setup → Duplicate Error Logs
Setup gear → Quick Find: Duplicate → Duplicate Error Logs.
- Review the list of recent errors
Each row: Error Date, Object, Action (Insert / Update), User, Error Message, Existing Record.
- Click into an error to see the full context
Detail page shows the matched record(s), the field values that triggered the match.
- Identify patterns
Same matching rule firing many times = the rule is too strict. Same user repeatedly hitting errors = process / training issue.
- Tune the matching rule or duplicate rule based on patterns
Setup → Matching Rules / Duplicate Rules → adjust criteria, action level.
Useful when one object's rule is firing many errors.
Identify users who repeatedly hit duplicate violations.
Insert / Update. Many orgs allow updates more permissively than inserts.
- Duplicate Error Logs only show Block-action errors. "Allow with Alert" violations are silent — they don't log here.
- The log shows the most recent N entries. For long-term tracking, build a scheduled report on the DuplicateRecordSet object instead.
- An integration's Insert call hitting a duplicate rule fails silently from the integration's perspective — the record isn't created. Wire integrations to read this page or the failure response.
How organizations use Duplicate Error Logs
Quarterly review of Duplicate Error Logs surfaced 40% false positives on Account; tightened matching rules and adoption rates jumped.
Operations uses the logs to identify integration patterns that produce duplicates upstream - fixing the source is more effective than fighting the rule.
Compliance team treats logs as evidence - duplicate-handling discipline is part of patient-data integrity audits.
Test your knowledge
Q1. Can a Salesforce admin configure Duplicate Error Logs without writing code?
Q2. What is the primary benefit of Duplicate Error Logs for Salesforce administrators?
Q3. Why is understanding Duplicate Error Logs important for Salesforce admins?
Discussion
Loading discussion…