De-duplication Tasks created for classes not in Health Inclusion rule via Discovery SourceIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } De-duplication tasks are created even though classes are not in the Inclusion rules .Only the following classes are added to the inclusion listLinux ServerAIX Server ✦༻❁༺✦✦༻❁༺✦ Question one: ✦༻❁༺✦✦༻❁༺✦ I have a customer who has a De-dup task created for Windows Server CI.However, he created a Health Inclusion rule for Duplicate that applies to cmdb_ci where class is Linux Server, and that's it.After running the Discovery on a Windows Server IP address that already had two CIs with almost duplicate fields.ServiceNow Discovery did not respect the Health Inclusion rule and created a De-Dup task.Does this mean that Health Inclusion rules are not taken into consideration if the Discovery Source creates the CI as duplicates in a deduplication task? ✦༻❁༺✦✦༻❁༺✦ Question two: ✦༻❁༺✦✦༻❁༺✦ Since I mentioned that the Health Inclusion rule for Duplicate applies to cmdb_ci where class is Linux Server, and that's it.The Dependent CI values for Linux Server, such as cmdb_ci_ip_address, cmdb_ci_disk, etc., have a Deduplication task created.If the Health Inclusion rule applies to a Linux Server, then why are dependent CI tasks considered at the time of the DeDup task?Is this also an expected behaviour? Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } No Release or Environment Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Regarding your first question about Health Inclusion rules and Discovery-created De-duplication tasks: Health Inclusion rules are designed to filter which CIs are considered during CMDB Health calculations and reporting. However, these rules do not directly control or restrict the Discovery process or the creation of De-duplication tasks by Discovery. Discovery’s deduplication logic operates based on its own matching and reconciliation rules when it identifies potential duplicate CIs during a scan. Therefore, even if a Health Inclusion rule limits health checks to Linux Server class CIs, Discovery can still create De-duplication tasks for Windows Server CIs if it detects duplicates. In other words, Health Inclusion rules do not prevent Discovery from creating deduplication tasks for CIs outside the scope of those rules. For your second question about dependent CIs (like cmdb_ci_ip_address, cmdb_ci_disk) having deduplication tasks despite the Health Inclusion rule applying only to Linux Server: Dependent CIs related to a Linux Server CI are included in deduplication tasks because Discovery’s deduplication process considers the entire CI hierarchy and related configuration items to maintain data integrity.Even if the Health Inclusion rule limits health checks to Linux Server class, Discovery’s deduplication tasks will still include dependent CIs to ensure duplicates are resolved comprehensively. This behavior is expected to avoid orphaned or inconsistent dependent CIs after deduplication. In summary, Health Inclusion rules affect CMDB Health calculations but do not restrict Discovery’s deduplication task creation, which operates independently and includes dependent CIs to maintain CMDB consistency.