I have two orgs, both have same duplicate rule and its matcing rule for contact, being active and first in order
In the first org, when i click convert list button, lead conversion screen opens, under contact, create contact is selected by default, and under choose existing contact, it shows 1 Contact Matches, but in second org, create contact is selected, and under choose existing contact, it shows 0 Contact Matches detected, when i click convert button in lead conversion screen, it throws "The records you're about to create look like duplicates. Consider choosing existing records." and only now, under choose existing contact, it shows 1 Contact Match, why so doesn't it show at the beginning itself
In 2nd Org, Duplicate Rule is triggered only when the convert button is clicked in lead conversion, but not when the screen is initially loaded. Why so, how to rectify it?
#Trailhead Challenges
Hey Enusha,
This lines up with a known distinction in how duplicate management works during lead conversion: the initial "X Contact Matches" panel on the Convert screen and the full check triggered when you click Convert are two separate evaluation passes, not the same rule execution. The initial on-load panel runs a lighter-weight lookup that's more reliable with standard fields, while the full duplicate rule engine (the one that blocks/warns on Convert) always fully evaluates your configured Matching Rule regardless of field type. That explains exactly what you found: standard field alone works on load, but custom field (or standard+custom combo) only gets properly evaluated at the Convert/Save-time check, not the initial screen render.
If you want a permanent fix rather than just working around it, log a case with Salesforce Support referencing this exact repro (2 orgs, same rule, different field-type-based behavior on initial load vs. save), since inconsistent behavior here is worth having them confirm as expected vs. a bug.
For now, practically: agents should know "0 matches shown" on load doesn't mean no duplicate exists if your rule includes custom fields, always click Convert and heed the warning rather than trusting the initial panel.
