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.
Service Mapping stops displaying connecting nodes at some point after discovery is complete - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Service Mapping stops displaying connecting nodes at some point after discovery is complete
KB0635224

Service Mapping stops displaying connecting nodes at some point after discovery is complete


953 Views Last updated : Jun 23, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

If you run a deep, top-down or vertical Service Mapping discovery, the discovered bottom nodes do not display outgoing connections to the next nodes even though the discovery logs tell you that these outgoing connections have been successfully created and no errors were found.

Resolution

The problem in this scenario is that Service Mapping discovery of the Business Service may have reached the depth of the service model recomputation.

You can increase the service model recomputation depth. To do this:

  1. Add the property named glide.service_mapping.computation_depth to the sys_properties table with a value of 30 (the default is 25). 
  2. Run the following script where 939137dd4ff4830056dc70021310c779 is the sys_id of the business service as an example:

 

var gr = new GlideRecord('cmdb_ci_service_discovered');
gr.get('939137dd4ff4830056dc70021310c779'); // the business service sys_id
var layerId = gr.layer;

var layerGr = new GlideRecord('svc_layer');
layerGr.get(layerId);

var env = sn_svcmod.ServiceContainerFactory.loadEnvironment(layerGr.environment);
var allLayers = env.layers();
for (var i = 0 ; i < allLayers.length ; i++) {
var layer = allLayers[i];
layer.markRecomputationNeeded();
}

SNC.ServiceMappingFactory.recomputeLayer(layerGr);

This script syncs the service model for the business service without deleting the history.

If you need to, you can increase glide.service_mapping.computation_depth and run the script 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.