SG-SolarWinds connections missing properties, data sources, and scheduled imports after instance cloneIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } After cloning a production ServiceNow instance to a sub-production instance, a configured SolarWinds Service Graph Connector fails to run. Connection properties and data sources appear missing, and the following error is generated at runtime: "No SolarWinds instance defined on sn_cmdb_int_util_service_graph_connection_property for connection alias" Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } After cloning a production instance to a sub-production instance, one or more of the following is observed on the target instance: The Service Graph Connection Properties, Service Graph Connection Data Sources, and Service Graph Connection Scheduled Data Imports related lists on SolarWinds connection records appear empty.Test Connection fails for the SolarWinds Service Graph Connector.Scheduled imports fail with the error: "No SolarWinds instance defined on sn_cmdb_int_util_service_graph_connection_property for connection alias."Records in sn_cmdb_int_util_service_graph_connection_property, sn_cmdb_int_util_service_graph_connection_data_source, and sn_cmdb_int_util_service_graph_connection_scheduled_data_import show an empty Service Graph Connection reference field when viewed directly. Facts<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } NOTE: This article is focused on SG-SolarWinds but the same is likely applicable for other ServiceNow-supported SGCs that utilize SGC Central. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Service Graph Connector for SolarWinds version 2.6.0 and later. Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The Service Graph Connector for SolarWinds stores its connection configuration across four related tables: sn_cmdb_int_util_service_graph_connection, sn_cmdb_int_util_service_graph_connection_property, sn_cmdb_int_util_service_graph_connection_data_source, and sn_cmdb_int_util_service_graph_connection_scheduled_data_import. None of these tables are included in ServiceNow's default clone exclude list. When a production-to-sub-production clone is performed without custom Clone Exclude and Data Preserver entries for these tables, the clone overwrites the target instance's SGC configuration with production data. The connection records themselves are copied intact, but the Service Graph Connection reference field on property, data source, and scheduled import records holds a production connection record sys_id that has no matching record on the target instance. The reference resolves to nothing, causing the related lists to appear empty and the runtime lookup to fail. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Re-associate the Service Graph Connection reference field on all affected records across the three related tables. The record names are intact after the clone and can be used to identify the correct target connection. For multi-instance SolarWinds configurations, the suffix in each record name (for example: EMEA, DEV) maps directly to the corresponding connection record. Navigate to sn_cmdb_int_util_service_graph_connection_property_list.do on the target instance, filtered by Application = Service Graph Connector for SolarWinds. For each record, open the record and set the Service Graph Connection field to the appropriate connection record.Navigate to sn_cmdb_int_util_service_graph_connection_data_source_list.do, filtered by Application = Service Graph Connector for SolarWinds. For each record, open the record and set the Service Graph Connection field to the connection record whose name matches the regional suffix in the data source name.Navigate to sn_cmdb_int_util_service_graph_connection_scheduled_data_import_list.do, filtered by Application = Service Graph Connector for SolarWinds. Apply the same regional suffix matching to set the Service Graph Connection field on each scheduled import record.Once all records are reassociated, open each connection record and confirm that the Service Graph Connection Properties, Data Sources, and Scheduled Data Imports related lists are now populated correctly.Use Test Connection on each connection record to confirm connectivity, then run a Test Load (20 records) on at least one data source per connection to confirm the runtime error is resolved before re-enabling scheduled imports. To prevent recurrence on future clones, add the following four tables to both the Clone Exclude list and the Clone Data Preserver list in the applicable clone profile before each clone. A table added to excludes without a corresponding Data Preserver entry will be emptied entirely on the target instance. sn_cmdb_int_util_service_graph_connectionsn_cmdb_int_util_service_graph_connection_propertysn_cmdb_int_util_service_graph_connection_data_sourcesn_cmdb_int_util_service_graph_connection_scheduled_data_import