Detection Engine

Detection Engine controls how Data Cleanser’s scalable duplicate-detection pipeline batches work during a scan. Most orgs leave the default alone; raise or lower the index batch size only when an administrator is tuning large-object performance.

This settings panel is separate from the Merge Engine page (how records are merged). Detection Engine settings affect scanning and indexing, not merge DML.

Open Detection Engine settings

1. Open the Settings tab.
2. Choose Detection Engine in the sidebar (second item, under Merge Display Defaults).

Viewing and saving these settings requires the custom permission Data_Cleanser_Match_Engine_Admin (included on the Data_Cleanser permission set). Users without it see an access message and cannot change the batch size. Typical end users on Data_Cleanser_User do not need this panel.

Index batch size

What it is

The number of records processed per index batch while the detection engine builds and compares match keys during a duplicate scan.

Default

1000

Allowed range

1–2000 (whole numbers only)

When to change it

Lower the value if scans hit governor or heap pressure on very large objects or heavy custom fields. Raise it (within the limit) only when administrators have confirmed the org can sustain larger batches.

Click Save after changing the value. An “Unsaved changes” banner appears while edits are pending. Invalid values (blank, non-integer, or outside 1–2000) cannot be saved.

What this setting does not control

• Mass-merge batch size or merge DML caps — see Merge Engine and Multi-Select & Mass Merge.
• Data Quality scoring batch behavior — see Data Quality Scheduling.
• Which objects are scanned — see Objects Settings.