Migration from Probe to Pattern causing hundreds of De-Duplication Tasks

[Lisa O_Brien]

Since we've migrated to Patterns, there are hundreds of De-Duplication tasks being created daily, in the following classes:    Memory Module, File System, Disk Partition, and Disk.     They all have a Discovery Source of ACC-Visibility.    They all depend on a Computer CI.    There doesn't seem to be any difference in the dups besides the correlation id.    Has anyone else run into this ?   Any suggestions on how to stop the De-Duplication tasks from being created ?

[Anshu_Anand_]

Can you check the IRE rules here.

Duplicates are created only when IRE fails.

Also please check if the discover source of ACC_Visibility are coming in the cmdb via IRE . 

[Lisa O_Brien]

Thank you for your response.      How can I check to see if Discovery source of ACC_Visibility is coming in to the CMDB via IRE ?     

[Ashok Sasidhara]

You can check CMDB 360 for insights about data populated from various sources. It is explained in the following URL:

https://docs.servicenow.com/bundle/washingtondc-servicenow-platform/page/product/configuration-manag...

Also you can check my article below for information about IRE:

https://servicenowguru.com/cmdb/servicenow-cmdb-identification-and-reconciliation-engine-ire/

[Anshu_Anand_]

There is already a KB for this for softwares for ACC.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0962842