What is the skip_sync field on Asset or CI recordIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } It is used to tell the Asset-CI Synchronisation code to not sync from the CI to the Asset, or Asset to the CI, as part of the record update() that is about to happen. 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 field on Asset and CMDB CI records shouldn't be considered a proper field/column at all. It can be set as if it were a field, in the normal way, on Asset and CMDB CI GlideRecords in code, but exists only in memory, only during the current transaction. The skip_sync flag is set to false by default. If set to true on a record, the Asset-CI Sync business rules will not run on the next update for that record. But if you do see the actual field set as True in a record, then something must have gone wrong. There are OOB script includes and business rules that will be involved in any CI or Asset update: AssetAndCISynchronizer: /sys_script_include.do?sys_id=9ec37b411b012000e49bfbcd2c071380Update Asset fields on change: /sys_script.do?sys_id=31e93aaf1b3210002502fbcd2c0713d8Update CI fields on change /sys_script.do?sys_id=4d15855c1b0310002502fbcd2c071399 Without the skip_sunc flag, the two business rules above would be triggered twice during an Asset-CI synchronization, and would be infinite if it were not for the platform's Recursion prevention code.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. It can also be used in: Business rules. 'Update Asset fields on change'/'Update CI fields on change' are the main and original user of this. e.g. a CI update will want the BR to update the linked asset, but doesn't want BRs running for that Asset update to update the CI back again.A business rule running at an order before those out-of-box ones can set it, and prevent them running.In GlideRecords in scripts, prior to making a .update(). You may want to do an update to a record from e.g. a scheduled script, but can't use .setWorkflow(false) because you do still need business rules/engines to run, but do not want the 'Update Asset fields on change'/'Update CI fields on change' business rule to run.In IRE input payloads.There are several examples in the docs of "skip_sync": "0", being used in the payload JSON. This would guarantee the insert/update starts with the default skip_sync=false. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Any Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } N/A