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.
CI discovered once change is closed - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • CI discovered once change is closed
KB0695192

CI discovered once change is closed


651 Views Last updated : May 22, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Overview


Change requests often have a configuration item associated with the change. A discovery of the configuration item will be triggered if discovery is installed and configured. The "created by" field in the discovery will reflect the user that closed the change.

Solution


The business rule "Run rediscovery after change request" triggers the discovery. This business rule checks on sys_property "sa.redisovery_after_change" to determine if the discovery should be triggered after a change is closed.

Such discoveries can be avoided by either:

  1. Disabling the business rule "Run rediscovery after change request"
  2. Set "sa.rediscovery_after_change" = false, the property may need to be created if it does not already exist in the environment

Conditions can be added to the business rule to limit the roles of users that can trigger such discoveries.

Additional Information


The discovery will be triggered even if the user does not have the roles necessary to create a discovery. This is expected behavior, otherwise all users closing changes would need discovery admin roles. The behavior can be modified as described in the "Solution" section of this KB article.


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.