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.
discovery_source field is switching between "unknown" and empty values - Product Knowledge
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • discovery_source field is switching between "unknown" and empty values
KB0695325

discovery_source field is switching between "unknown" and empty values


4310 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms


Discovery source is switching between "unknown" and empty values

Release


Any release

Cause

The "discovery_source" is a mandatory parameter for Identification Reconciliation Engine. CMDB Health audit job for duplicate processor will be triggered when CMDB Health Dashboard scheduled jobs are kicked off. This will pick up CI records which have empty value for the discovery source field for evaluation, as they might have go through Identification Reconciliation Engine. Once the evaluation is done, it marks the CI discovery source as "unknown".

This "unknown" status will reset to empty whenever there is an update to CI record to ensure that it is picked for duplicate evaluation. This done by a business rule "Reset Unknown Discovery Source State" which is triggered when there is an update to the CI

This can happen in a loop when the CMDB health job is run everyday, and there is a update to the CI

Resolution


In order to break the loop, make sure that the "discovery_source" is not empty for the CI's, it needs to be of any value, so that it would not be set and reset from "unknown"

 


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.