Issue: We observed that the duplicate opportunities were created even if the condition is met the DeDup engine was failing to mark it as duplicate, when the Opportunity Capture API was hit multiple times for the same opportunity.
Root Cause: So when we checked the De-Dup logic with DEV we found the issue was mainly due the “Is-Not”
operation used in the field Status and Stage and the concurrent hit of Opportunity Capture API.
IS NOT operator is not recommended to be used for field which have static values.
PFB the screenshot for the condition:
So in this if we see the Status field the condition which was set is “Is Not Won or Lost “, so which ideally translates to is Open. So it’s recommended to use IS operator whenever possible rather than IS NOT operator.
This is not reproducible through Postman, when we post through postman it will not be at the same time stamps, there will be few seconds to minutes delay, however the client was hitting the API multiple times at the same time stamp just seconds difference.
Solution:
So for these cases, for the De-Dup engine to handle the load and not miss any payload, we have a backend setting which needs to be enabled. post that the request will go In-Queue to the De-Dup engine and one settings for making sure it handles static values.
Once the above mentioned settings and changes were done, the Duplicates were detected correctly there were no failure in the De-Dup Engine.
