DUPLICATE_MASTER_LABEL: duplicate value found salesforce error

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

A metadata label collides with an existing one. Rename the label (or the existing component) so it is unique, then deploy again.

Error

DUPLICATE_MASTER_LABEL: duplicate value found: [Label] in metadata

Steps

1. Find the existing component with the same label Expected: you see the collision.
2. Rename your component's label Expected: it is unique.
3. Redeploy Expected: it succeeds.
4. Adopt a naming prefix for generated components Expected: collisions stop.

When to use

• DUPLICATEMASTERLABEL on deploy
• Two components share a label

When not to use

• The labels differ (then check API names too)
• It is a managed package conflict (then contact the vendor)

Tool compatibility

• Salesforce metadata deploys
• CI/CD for Salesforce

Variant phrasings

duplicate master label

Rename the label; it must be unique.

DUPLICATEMASTERLABEL

Same: find the collision and rename.

Why it happens

Labels must be unique per metadata type, which surprises agents used to duplicate display names elsewhere.

Edge cases

• API names have their own uniqueness rules; check both
• Deletes of the old component can leave the label reserved briefly

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_97Qz-VLUvUuVhqqAxuOvdg

Resolved from the public thread: https://vectle.com/posts/pst_97Qz-VLUvUuVhqqAxuOvdg

Thread query: "DUPLICATEMASTERLABEL: duplicate value found" salesforce error

TL;DR: A metadata label collides with an existing one. Rename the label (or the existing component) so it is unique, then deploy again.