Limitations and Troubleshooting
Platform boundaries, common failure modes, and an administrator pre-flight checklist. Use this when user-facing troubleshooting steps are not enough.
What Data Cleanser does not do
- No Salesforce Duplicate Management integration — does not read or write Duplicate Rules, Matching Rules, or Duplicate Record Sets.
- No custom object scanning — Account, Contact, Lead only.
- No transitive grouping — see Duplicate Groups & Scan Architecture.
- Rollback requires Pro + Rollback — without that license, merges follow native Salesforce behavior and cannot be rolled back.
Hard limitations and edge cases
- Blank match components omitted from keys — can cause unexpectedly broad groups.
- Fuzzy = Soundex equality only — not Levenshtein / edit-distance (see Match Rules — Technical Reference).
- Street normalization: only CRESCENT, ROAD, STREET abbreviations.
- Mass merge: max 20 members scored per group; 10 groups per batch.
- Manual merge: max 30 losers per API call.
Not_duplicate__cexists but scan queries do not filter on it today.- Scheduled scans do not auto-merge (
Auto_Merge__cunused by scheduler). - Review queue empty until scan completes — not incremental streaming.
- Experience Cloud / guest users not supported — authenticated CRM users expected.
- Only one enabled scenario per object type should be active for grouping.
Advanced troubleshooting
| Symptom | Likely cause | Where to look |
|---|---|---|
| “Duplicates” that should not match | Blank field omitted from key; partial key match | DCM_Duplicate_Key_Re__c on records; tighten rules |
| Expected chain not grouped | No transitive closure | Add rule producing one shared key for A, B, and C |
| Fuzzy too loose or too strict | Phonetic Soundex, not spelling distance | Word Mapping or Exact instead of Fuzzy |
| Group missing from Review | Roll-up ≤ 1 or scan still processing | Wait for scan; check EnabledStatus__c |
| Queue empty during scan | By design until scan completes | Home alerts; Starting Scans |
| Mass merge wrong survivor | Master rule scoring | Master rules; manual merge override |
| Overflow did not save email/phone | Overflow is Description-field choices | Select overflow values; confirm Overflow ON |
| Schedule did not run | Day__c format mismatch |
Duplicate_Scheduler__c rows vs scheduler format |
| Schedule ran but nothing merged | Scheduler scans only | Expected — run Review or mass merge manually |
| Merge failed mid-batch | Validation rule, sharing, native duplicate rule | Settings → Warnings |
| Trial blocked unexpectedly | Multi-select counts merges upfront | Settings → License; reduce selection size |
| Records missing in workbench | Sharing or FLS | Permission set + record access |
Administrator pre-flight checklist
- Review validation rules on Account, Contact, Lead that fire on merge/update.
- Confirm required fields on survivors can be populated from losers.
- Check Salesforce Duplicate Rules — native rules may block merge DML independently.
- Verify sharing: users only see and merge records they can access.
- Confirm Person Account configuration and Name field handling.
- Configure Lead conversion preferences for cross-object scenarios.
- Assess Batch Apex capacity; default scan batch size is 100 on install.
- Assign Data_Cleanser_User permission set to merge operators.
- Grant FLS on package fields (
DCM_Duplicate_Key__c,DCM_Master_Score__c, etc.). - Confirm users have standard merge rights on target objects.
Reset Database — technical detail
Reset Selected Object
Deletes duplicate groups
CRM records untouched
Deletes Duplicate_Group__c and junction records for ticked types.
Re-run a scan to rebuild groups.
Reset Variables
Restores defaults
Scenarios retained
Resets Data Cleanser settings and preferences to defaults.
Does not delete scenarios or CRM data.
See Settings Reference for the user-facing description.
Still stuck?
Start with Troubleshooting & Quick Reference for everyday errors. For match-key or batch-job investigation, continue with Match Rules — Technical Reference and Administration Guide.