When the "Started probe" and "Completed probe" fields are equal during CMP discovery, the discovery status 'Completed' field is updated by the Business Rule on ECC queue 'Discovery - Sensors' and the Duration gets mistakenly updated without waiting for the schedule to finish executing. 


Steps to Reproduce

  1. Create Cloud Account and add an AWS Datacenter.
  2. Run discovery.
  3. In the discovery status, when the started and completed are equal, the duration is set to complete even before discovery is complete.
  4. Discovery will continue to run and keep updating the discovery status.
  5. When the discovery finally completes, the duration will not be updated.

This issue will be reproducible only when the started and completed are equal before the completion of all steps in discovery. 


As a workaround, you may import the attached Business Rule to the affected instance "sys_script_5c1e5ddf0a0a0b1c00e73c6712aa796b_discovery_status completed to active BR". 

This business rule will delay the discovery status completion calculation enough to assure if there are still any related probes triggered, they are calculated prior the changing the state to "Completed". 


This issue is under review. To receive notifications when more information is available, subscribe to this Known Error article by clicking the Subscribe button at the top right of the article. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.



After upgrading to a ServiceNow release/patch with PRB1291131 fix , please deactivate the imported business rule.

Related Problem: PRB1291131

Seen In

There is no data to report.

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-04-22 03:12:28
sys_script_5c1e5ddf0a0a0b1c00e73c6712aa796b_discovery_status completed to active BR.xml