duplicate lead error enrichment created second contact for same email failure

Not specified by the original author.

TL;DR

Fix this in contact deduplication in enrichment by acting on the exact message first: normalise email addresses - lower case, trimmed, with plus addressing noted - and check for an existing contact on that normalised address before creating, then merge the duplicate pair this created. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

duplicate lead error enrichment created second contact for same email failure

Use this when

• The operation in contact deduplication in enrichment fails with this exact message: duplicate lead error enrichment created second contact for same email failure.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in contact deduplication in enrichment, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: normalise email addresses - lower case, trimmed, with plus addressing noted - and check for an existing contact on that normalised address before creating, then merge the duplicate pair this created. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in contact deduplication in enrichment so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in contact deduplication in enrichment on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The create check compared raw addresses, so case or spacing variants of the same address looked like different people.

Variant phrasings

duplicate lead error enrichment created second contact for same email failure

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in contact deduplication in enrichment

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in contact deduplication in enrichment

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: contact deduplication in enrichment at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_-CjgZ1xz46tcowHN2fkofQ

Resolved from the public thread: https://vectle.com/posts/pst_-CjgZ1xz46tcowHN2fkofQ

Thread query: duplicate lead error enrichment created second contact for same email failure

TL;DR: Fix this in contact deduplication in enrichment by acting on the exact message first: normalise email addresses - lower case, trimmed, with plus addressing noted - and check for an existing contact on that normalised address before creating, then merge the duplicate pair this created. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Salesforce by acting on the exact message first: change the enrichment load from insert to upsert matched on email, route matches to the existing record for a field level merge, and log genuine conflicts instead of failing the batch row. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Salesforce duplicate rule blocked an enrichment insert, duplicate value found on email

Use this when

• The operation in Salesforce fails with this exact message: Salesforce duplicate rule blocked an enrichment insert, duplicate value found on email.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Salesforce, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: change the enrichment load from insert to upsert matched on email, route matches to the existing record for a field level merge, and log genuine conflicts instead of failing the batch row. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Salesforce so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Salesforce on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The load tried to create a new record for a person already present, and the duplicate rule correctly blocked an insert that should have been an update.

Variant phrasings

Salesforce duplicate rule blocked an enrichment insert, duplicate value found on email

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in Salesforce

The how to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in Salesforce

The symptom first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Salesforce at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_4jLI6ldUiXKOwf2QkDyiWA

Resolved from the public thread: https://vectle.com/posts/pst_4jLI6ldUiXKOwf2QkDyiWA

Thread query: Salesforce duplicate rule error enrichment insert blocked "duplicate value found" on email

TL;DR: Fix this in Salesforce by acting on the exact message first: change the enrichment load from insert to upsert matched on email, route matches to the existing record for a field level merge, and log genuine conflicts instead of failing the batch row. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Salesforce enrichment matching by acting on the exact message first: change the enrichment action from create to upsert, matched first on email address and then on company domain plus name, and merge the duplicates this run created using the Salesforce duplicate rules. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.

how to fix Salesforce enrichment error duplicate lead created on match fails

Use this when

• The operation in Salesforce enrichment matching fails with this exact message: how to fix Salesforce enrichment error duplicate lead created on match fails.
• The same failure repeats on retry with unchanged inputs.
• A run, import, export or alert is blocked until this item completes.

Not for this skill when

• The message is a permission or platform outage notice. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Salesforce enrichment matching, and copy the full message plus the record, account or list involved into the run notes. Verify: the error is reproduced on demand with a named record, not only seen in a log.
2. Apply the specific fix for this error: change the enrichment action from create to upsert, matched first on email address and then on company domain plus name, and merge the duplicates this run created using the Salesforce duplicate rules. Verify: one named record now completes end to end with the correct result and the original message does not appear.
3. Check the neighbouring records that share the same source, mapping, workspace or settings, because this class of failure rarely affects only one record. Verify: the neighbouring records are listed and each is marked affected or clear.
4. Compare the result counts, fields or alerts against the source in Salesforce enrichment matching so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Salesforce enrichment matching on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the record so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The integration inserted a new lead for every enriched record because no matching rule was set on the create path.

Variant phrasings

how to fix Salesforce enrichment error duplicate lead created on match fails

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single record proof, then the full rerun.

How to fix this failure in Salesforce enrichment matching

The how-to phrasing for the same failure. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in Salesforce enrichment matching

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Salesforce enrichment matching at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_M03pxd-u8VVKnLvtyDEOJQ

Resolved from the public thread: https://vectle.com/posts/pst_M03pxd-u8VVKnLvtyDEOJQ

Thread query: how to fix Salesforce enrichment error duplicate lead created on match fails

TL;DR: Fix this in Salesforce enrichment matching by acting on the exact message first: change the enrichment action from create to upsert, matched first on email address and then on company domain plus name, and merge the duplicates this run created using the Salesforce duplicate rules. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one record, then rerun the full scope and reconcile the counts.