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.
What is the skip_sync field on Asset or CI record - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • What is the skip_sync field on Asset or CI record
KB0743665

What is the skip_sync field on Asset or CI record


2893 Views Last updated : Apr 29, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

For the latest information on this topic, see Configuration Item [cmdb_ci] class.

The skip_sync field not only exists on assets but also on the CMDB table. It is the flag indicating whether synchronization between Asset and CMDB can be skipped.

There are OOB script includes and business rules that may invoke according to functions and change the value of skip_sync:

  • AssetAndCISynchronizer: /nav_to.do?uri=sys_script_include.do?sys_id=9ec37b411b012000e49bfbcd2c071380
  • Update Asset fields on change: /nav_to.do?uri=sys_script.do?sys_id=31e93aaf1b3210002502fbcd2c0713d8
  • Update CI fields on change /nav_to.do?uri=sys_script.do?sys_id=4d15855c1b0310002502fbcd2c071399

The skip_sync flag is used to prevent recursion within the same cycle of business rules and will be reset in the next cycle during Asset-CI synchronization. The skip_sync flag is set to false by default.

As the two business rules above would be triggered twice during an Asset-CI synchronization. The skip_sync flag would be set to false again after the synchronization. In case the skip_sync flag was set to true for some reason, an update on the Asset/CI should help set the flag back to false.


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.