Common AutoMerge Errors
Various errors can occur while you are AutoMerging duplicates. Timeout and Analysis Rules errors are the most common.
Timeout errors
Timeouts come down to the size of a particular set and how many related records a merge has to cascade to, not the number of sets you select. Time of day can matter too.
What to do: lower the Maximum Duplicate Set Size setting first. See Timeout errors for the full explanation and further fixes.
Analysis Rules errors
These mean the Analysis Rules configuration is incomplete, or references a field that no longer exists on the entity.
What to do: open the Analysis Rules record and confirm the entity definition, matching rules, ranking rules, and precision rules are all present and reference valid fields.
The most common version of this: a rule references a field that was never added to the Entity Definition. See Matching rules.
Connection errors
If AutoMerge can't reach your CRM at all, an expired Azure client secret on the CRM connection record is the likely cause.
What to do: use the Verify function on the CRM Connection record. It checks the credentials and surfaces any issue with them. See Azure app user.
Privilege errors during merge
If tagging works but merging fails, the connection's application user probably lacks merge privileges.
The AutoMerge Analysis/Tagging AppUser - Minimum Privs security role is deliberately minimal: enough to analyze and tag, not enough to merge. That only matters for requests submitted with Operation = AutoMerge from the Management App; merges performed by users inside the CRM run under their own roles.
See Azure app user for the trade-off.
Contact us at sales@genbil.com with the error text and roughly when it occurred, and we can check the service logs.