We have observed an issue where a high number of duplicate tasks are getting attached to a single RCTASK under Duplicate Audit Results.
This is leading to overcrowding of duplicate records within one RCTASK, which impacts analysis and usability.
We would like to understand:
Why multiple duplicate tasks are being attached to a single RCTASK
Which rule, configuration, or logic controls this deduplication behavior
Where we can change or restrict the deduplication count, so that excessive duplicate tasks are not attached to the same RCTASK
Whether this behavior is controlled via:
Deduplication rules
Event Management / RCTASK configuration
Business Rules
System properties
Identification or correlation logic
Has anyone faced a similar issue, and what is the recommended way to limit or control duplicate audit results being linked to one RCTASK?
Any guidance on identifying the source of this behavior and best practices to resolve it would be greatly appreciated.
