Stratus Cloud Solutions Stratus Docs
Documentation / Data Cleanser User Guide / Advanced Reference

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.
  • Custom objects require Enterprise — subscriber custom object scanning and merge need an Enterprise or Enterprise + Rollback license (Trial can evaluate). See Custom Objects.
  • 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__c exists but scan queries do not filter on it today.
  • Scheduled scans do not auto-merge (Auto_Merge__c unused 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
  1. Review validation rules on Account, Contact, Lead that fire on merge/update.
  2. Confirm required fields on survivors can be populated from losers.
  3. Check Salesforce Duplicate Rules — native rules may block merge DML independently.
  4. Verify sharing: users only see and merge records they can access.
  5. Confirm Person Account configuration and Name field handling.
  6. Configure Lead conversion preferences for cross-object scenarios.
  7. Assess Batch Apex capacity; default scan batch size is 100 on install.
  8. Assign Data_Cleanser_User permission set to merge operators.
  9. Grant FLS on package fields (DCM_Duplicate_Key__c, DCM_Master_Score__c, etc.).
  10. Confirm users have standard merge rights on target objects.
Reset / Clear — technical detail

What is cleared

Package working data CRM records untouched

Depending on checkboxes: scenario activation flags, mass-merge running context, Duplicate_Group__c / Cross_Object_Group__c, match telemetry (Match_Run__c and staging), warnings, merge history, scenario definitions, and preference defaults.

Re-run a scan to rebuild groups after clearing them.

What is never cleared

CRM Account / Contact / Lead

License data and CRM records are never deleted by Reset / Clear.

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.