"DUPLICATE_VALUE: duplicate value found" salesforce upsert

Not specified by the original author.

TL;DR

Upsert matched more than one record, or the external id value already belongs to another record: your key is not unique in practice. Query for every record carrying that external id value, fix the source data so the key is truly unique, and confirm the field is marked unique and external id.

Error

[ {
  "message" : "duplicate value found: External_Id__c duplicates value on record with id: 001...",
  "errorCode" : "DUPLICATE_VALUE",
  "fields" : [ "External_Id__c" ]
} ]

Steps

1. Query for all records with the colliding value: SELECT Id, Name FROM Account WHERE ExternalId_c = '[value]'. Expected: you see every record sharing the key.
2. Decide the survivor: usually the oldest or the one with the most activity. Expected: one canonical record per key value.
3. Fix the source data so each row carries a distinct external id; blank or placeholder ids shared across rows are the usual cause. Expected: no two rows share a key.
4. In Setup, confirm the field is marked both Unique and External ID. Expected: Salesforce enforces uniqueness going forward instead of failing at upsert time.
5. Re-run the upsert. Expected: each row updates its one matching record or inserts cleanly.

When to use

• Upsert fails with DUPLICATE_VALUE naming an external id field.
• A backfill upsert worked on a sample but fails on the full file (duplicate keys in the full data).
• The error names a record id different from the one you expected to update.

When not to use

• DUPLICATES_DETECTED (duplicate rule, not key collision).
• "required field missing" (absent data, not duplicate data).

Tool compatibility

• Salesforce REST, SOAP, and Bulk API upserts by external id.
• Data Loader upsert operation and agent upsert loops.

Variant phrasings

duplicate value found on record with id

The message names the existing record; open it to compare.

DUPLICATE_VALUE on standard fields

Email or other unique standard fields collide the same way.

Why it happens

Upsert is "update if exactly one match, insert if zero". Source data with blank keys, placeholder keys like "TBD", or real duplicates in the file breaks the exactly-one assumption.

Edge cases

• Case-insensitive unique fields treat "ABC" and "abc" as the same; normalize case in the source.
• Leading and trailing whitespace makes two keys look different to humans but identical to Salesforce; trim in the source.
• Merging two records that share an external id needs the survivor chosen first, or the merge itself throws.

Provenance

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

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

Thread query: "DUPLICATE_VALUE: duplicate value found" salesforce upsert

TL;DR: Upsert matched more than one record, or the external id value already belongs to another record: your key is not unique in practice. Query for every record carrying that external id value, fix the source data so the key is truly unique, and confirm the field is marked unique and external id.

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

Never create a contact without first searching for an existing one on a stable key, usually the email address. Use the CRM's upsert or create-or-update endpoint with that key so a second run updates instead of duplicating. The dedupe check happens before the create call, every time, no exceptions.

agent created duplicate HubSpot contacts because dedupe key was missing

Use this when

• the CRM has two or more contacts for the same person
• reruns of the agent create fresh contacts
• no lookup happens before the create call

Not for this skill when

• duplicates came from a CSV import (dedupe the file first)
• you need to merge existing duplicates (use the CRM merge tool)
• the contact data itself is wrong (fix the source)

Steps

1. Pick the dedupe key: email address first, falling back to a stable external id. Verify: the key is documented and every run uses the same one.
2. Before creating, search the CRM for the key. Verify: a known contact returns exactly one match.
3. If a match exists, update it; only create when there is no match. Verify: running the agent twice on the same input adds zero contacts.
4. Use the CRM's upsert endpoint where available so the check and write are atomic. Verify: concurrent runs do not both create.
5. Log every create with the dedupe key value for later audit. Verify: you can trace any contact back to the run that made it.

Tool/version compatibility

HubSpot, Salesforce, and most CRMs expose search plus upsert. The pattern is the same everywhere.

Why it happens

The agent's flow is gather data, create contact, with no lookup step. Each run treats every person as new because nothing ever asks whether this person exists already.

Edge cases / pitfalls

• Email addresses change; keep the external id as the long-term key and email as the lookup.
• Case and whitespace differences defeat naive matching; lowercase and trim the key before comparing.
• A failed search that returns no match on error will mass-create duplicates; treat search errors as blocking, not as empty.

Variant phrasings

CRM filled with duplicate contacts after agent runs

Short version: create without lookup.

Every rerun added the same contacts again

Short version: missing dedupe key on create.

Provenance

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

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

Thread query: agent created duplicate HubSpot contacts because dedupe key was missing

TL;DR: Never create a contact without first searching for an existing one on a stable key, usually the email address. Use the CRM's upsert or create-or-update endpoint with that key so a second run updates instead of duplicating. The dedupe check happens before the create call, every time, no exceptions.