Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
CMDB Dashboard not detecting duplicate CIs - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • CMDB Dashboard not detecting duplicate CIs
KB0754378

CMDB Dashboard not detecting duplicate CIs


1294 Views Last updated : Jul 24, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms

CMDB Dashboard not detecting duplicate CIs

Release

All

Cause

The duplicate process only query for records with the following conditions: 
(discovery_source=Unknown and updated on last 1 day) OR (discovery_source=empty)  

The reason for this query is:

  1. If a CI has a proper discovery_source, it should have been ran though Identification Engine or has been reconciled properly.
  2. The CI's with discovery_source = empty most likely hasn't been passed through Identification Engine yet.
  3. The CI with discovery_source = Unknown are the ones marked by the job itself so health results should have been generated. If the job failed the first time around the CI  discovery_source will be set up as Unknown and it it's over 1day old the duplicate jobs will not run on those CI.

Resolution

  1. Create a Reconciliation Definitions of each individual classes you wish to the rule to run on.  If you set it for the cmdb_ci_cluster (parent) it will not affect (child) cmdb_ci_win_cluster. 
  2. Set the discovery_source of all the CI to blank and rerun the health job again.

 


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.