Duplicate CIs created when Cloud Insights Billing runs after SGC because SGC did not create data center relationship - Support and Troubleshooting

Duplicate CIs created when Cloud Insights Billing runs after SGC because SGC did not create data center relationship .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: ; } } Issue Duplicate cmdb_ci_vm_instance CIs are created when Cloud Insights Billing runs after the Service Graph Connector for AWS because the SGC-created CI is missing the data center relationship.

Symptoms Two cmdb_ci_vm_instance CIs exist with the same Object ID but different sources The SGC-created CI has no relationship to a data center The Billing-created CI has a relationship to the AWS data center sys_object_source shows two different creation sources for the same resource Cause The billing pipeline calls IdentificationEngineScriptableApi.createOrUpdateCI() via DiscoveryCMDBUtil.insertOrUpdate() , setting Object ID, service account, and data center. The SGC uses DiscoveryAWSRelationshipSensor.findAndCreateRelationToVM() to create the DC relationship, but when this fails, IRE merges by source_recency_timestamp and does NOT combine relationship data. The newer payload overwrites the older one, creating a duplicate.

Resolution Check SG-AWS version. PRB1943428 fixes a credential swap issue in SG-AWS 2.1.3. If on 2.1.3+, investigate why SGC is not creating the DC relationship. Verify cmdb_ci_aws_datacenter exists with correct object_id for the region. Verify service account configuration. As a workaround, delete the duplicate and re-run SGC before billing. Route to SGC team if DC relationship still not created.