salesforce duplicate rule blocked case insert

Not specified by the original author.

TL;DR

A duplicate rule blocking Case insert means the new Case matched an existing record under the rule's matching criteria and the rule is set to block. Do not fight it per record: decide whether the match is a true duplicate (dedupe at the source) or a false positive (tune the matching rule), and give integrations a sanctioned bypass for the cases that must insert regardless. Blocking rules are data quality doing its job loudly.

The query

salesforce duplicate rule blocked case insert

Use this when

• Case inserts fail on duplicate rules
• Integrations cannot create Cases reliably
• You are tuning duplicate matching rules
• Auditing duplicate-rule blocks

Not for

• Overall deduplication strategy
• Account or contact merge rules
• Lead duplicate handling
• Duplicate job scheduling

Steps

1. Read the block as a match report, not just an error

The block response names the rule and the matched records. Read both: the rule tells you which criteria fired, the matched records tell you whether the match is correct. Most fixes start here.

Expected output: rule and matched records identified per block.

2. Decide true duplicate versus false positive

If the matched record really is the same case, fix the source: dedupe before insert, or update the existing Case instead. If the match is wrong (overly fuzzy criteria), the fix belongs in the matching rule, not in bypasses.

Expected output: each block classified as true or false positive.

3. Tune the matching rule for false positives

Loosen fuzzy thresholds or add discriminating fields (exact email plus subject, not just subject) so legitimate distinct Cases stop matching. Test the tuned rule against historical blocks before deploying.

Expected output: matching rule with acceptable false-positive rate.

4. Give integrations a sanctioned bypass path

For Cases that must insert even on match (high-volume intake, real-time channels), use the platform's duplicate-bypass mechanism on the integration user. Bypasses are audited and deliberate, unlike per-record workarounds.

Expected output: integration inserts succeeding via sanctioned bypass.

5. Monitor block rate as a data-quality metric

Track blocks per rule over time. A rising block rate means either duplicate intake is growing (fix the source) or the rule is over-firing (tune it). The metric tells you which.

Expected output: per-rule block-rate monitoring.

Template: the checklist

Duplicate rule blocks:
[ ] Block read as a match report (rule plus records)
[ ] Blocks classified true duplicate vs false positive
[ ] Matching rule tuned for false positives
[ ] Sanctioned bypass for must-insert integrations
[ ] Block rate monitored per rule

Variant phrasings

duplicate rule preventing case creation

Steps 1 and 2. Read the match, classify it.

case insert blocked as duplicate

Steps 2 and 4. True dupes get sourced; must-inserts get bypass.

salesforce matching rule too aggressive

Step 3. Tune the criteria.

Why it happens

Duplicate rules evaluate at insert time against the whole Case table, and intake channels (web forms, email, integrations) happily submit the same issue repeatedly: retries, double-submits, customers opening multiple channels. The rule is the only thing standing between messy intake and a messy database. When it blocks, it is usually right about the data and wrong about the workflow.

Edge cases

• Bypass scope creep: bypasses granted for one integration get reused for others. Review bypass grants periodically.
• Alert versus block: consider downgrading to alert for rules with high false-positive rates; humans resolve, inserts proceed.
• Cross-object matching: Case-to-Case versus Case-to-other-object rules behave differently. Know which fired.
• Bulk API inserts: blocks inside bulk jobs need per-record handling; one block must not fail the batch.

Provenance

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

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

Thread query: salesforce duplicate rule blocked case insert

TL;DR: A duplicate rule blocking Case insert means the new Case matched an existing record under the rule's matching criteria and the rule is set to block. Do not fight it per record: decide whether the match is a true duplicate (dedupe at the source) or a false positive (tune the matching rule), and give integrations a sanctioned bypass for the cases that must insert regardless. Blocking rules are data quality doing its job loudly.

Not specified by the original author.

TL;DR

An active duplicate rule matched the incoming lead and blocked the insert. Check for the existing record first, merge instead of insert, or pass the duplicate-rule header to allow the save when your process intentionally allows dupes.

salesforce 400 INVALID_FIELD duplicate rule blocked lead insert

Use this when

• Lead insert returns 400 with INVALID_FIELD and a duplicate rule message.
• A bulk lead load dies on a handful of records.
• The rule fires on records that look unique to the sender.

Not for this skill when

• Validation rule errors, which name the validation rule.
• Required-field missing errors.
• Duplicate rule warnings that allow save, which are not errors.

Steps

1. Read the error to confirm a duplicate rule, not a validation rule, blocked the insert. Verify: the message references duplicate detection.
2. Find the matching existing lead with a SOQL query on the rule's matching fields. Verify: you can see the existing record that triggered the match.
3. Decide per record: update the existing lead, or merge the data into it. Verify: the merge logic is written down and tested on one record.
4. For bulk loads, pre-dedupe the file against existing records before sending. Verify: a rerun of the batch inserts zero conflicts.
5. If the process legitimately needs duplicates, set the duplicate-rule header to allow save on that integration user. Verify: the insert succeeds and the duplicate is logged.

Variant phrasings

salesforce duplicate rule blocked insert

Common phrasing of the block.

salesforce lead insert duplicate detected 400

The code-angle search.

duplicate rule header allow save salesforce

The header-angle search.

Compatibility: Salesforce REST and SOAP APIs; duplicate rules configured per object in setup.

Why it happens

Duplicate rules exist to keep the database clean; they run on every insert and match on fields like email, name, and phone. Agent-built integrations that insert without checking first hit the rule constantly, especially on re-runs.

Edge cases / pitfalls

• Matching is fuzzy by default; near-matches you consider distinct will still fire.
• The header choice applies per request; a second code path without it still blocks.
• Bypass permissions on the integration user defeat the rule silently; scope them tightly.
• Reporting on blocked saves needs the duplicate error objects; log them, do not swallow.

Provenance

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

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

Thread query: salesforce 400 INVALID_FIELD duplicate rule blocked lead insert

TL;DR: An active duplicate rule matched the incoming lead and blocked the insert. Check for the existing record first, merge instead of insert, or pass the duplicate-rule header to allow the save when your process intentionally allows dupes.

Not specified by the original author.

TL;DR

A duplicate rule that never fires is usually inactive, scoped to the wrong object, or using matching criteria too narrow for your data (exact name when the data has nicknames). Check the rule status and its matching rule, test it against a known duplicate pair, and widen the criteria deliberately. Also check whether the writer bypasses rules via the API header.

Error

(No error; the symptom is two contact records for the same person with no duplicate alert.)

Steps

1. In Setup, open Duplicate Rules and confirm the rule is Active and assigned to the right object. Expected: active, correct object, correct record types.
2. Open the matching rule and read its matching criteria. Expected: you see the fields and the matching method (exact vs fuzzy) for each.
3. Test with a known pair: create a contact that should match and see whether the rule fires. Expected: a controlled reproduction of the miss.
4. If the criteria are too narrow (exact first+last name but your data has "Bob" vs "Robert"), switch key fields to fuzzy or add email as an exact criterion. Expected: the test pair now triggers the rule.
5. Check API writers: the duplicate rule header allowSave bypasses Alert rules, and some integrations set it globally. Expected: you find whether the bypass is legitimate or a blanket skip.

When to use

• Duplicate contacts keep appearing despite an active duplicate rule.
• An agent bulk load created duplicates the UI would have caught.
• After changing matching criteria, duplicates still slip through.

When not to use

• DUPLICATES_DETECTED blocks (the rule fires too aggressively, opposite problem).
• HubSpot duplicates (different platform mechanics).

Tool compatibility

• Salesforce duplicate rules and matching rules; Setup audit.
• API duplicate rule headers.

Variant phrasings

duplicate rule not firing on import

Imports often bypass rules depending on the tool settings; check the import path.

matching rule too strict

Narrow criteria miss real duplicates; widen deliberately.

Why it happens

Matching rules are precise instruments tuned for clean data. Real CRM data has nicknames, typos, and married names, so exact-match criteria miss constantly while everyone assumes the rule is protecting them.

Edge cases

• Cross-object matching (lead vs contact) needs its own rule; a contact rule never fires on lead insert.
• Person accounts need separate matching consideration from business accounts.
• Widening too far creates false-positive blocks; tune on a labeled sample of true pairs.

Provenance

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

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

Thread query: salesforce duplicate rules failed to catch existing contacts

TL;DR: A duplicate rule that never fires is usually inactive, scoped to the wrong object, or using matching criteria too narrow for your data (exact name when the data has nicknames). Check the rule status and its matching rule, test it against a known duplicate pair, and widen the criteria deliberately. Also check whether the writer bypasses rules via the API header.