CMDB reconciliation error: conflicting data from multiple sources

Multiple data sources (Discovery, Service Mapping, External integrations) have the same precedence level and are providing different values for identical CI attributes during reconciliation. (high likelihood)

Data source precedence configuration is missing or incorrectly set in the IRE Data Source table (cmdb_ire_data_source), causing the system to treat sources as having equal priority. (high likelihood)

Custom reconciliation rules or transform maps are creating conflicts by allowing multiple authoritative sources to update the same fields without proper precedence hierarchy. (medium likelihood)

Time-based precedence conflicts where multiple sources updated the same CI attribute simultaneously or within the same reconciliation window, making it impossible to determine the authoritative value. (medium likelihood)

Duplicate or misconfigured identification rules are causing the same CI to be identified by multiple data sources as different objects, leading to conflicting merge operations. (low likelihood)

Step 1: Navigate to Configuration Management > Identification and Reconciliation > Data Sources to review all configured data sources and identify which sources are conflicting for the affected CIs.

Step 2: Check the IRE logs at System Diagnostics > Log > Application Log, filtering for 'cmdb' and 'reconciliation' to identify specific CIs, attributes, and data sources involved in the conflict.

Step 3: Review the Data Source Precedence by navigating to the cmdb_ire_data_source table and verify that each data source has a unique, appropriate precedence value (lower numbers indicate higher precedence).

Step 4: Adjust data source precedence by editing the 'Precedence' field in conflicting data sources, ensuring Discovery typically has precedence 100, Service Mapping 200, and external integrations 300 or higher based on trust level.

Step 5: Review and modify reconciliation rules at Configuration Management > Identification and Reconciliation > Reconciliation Rules to ensure field-level precedence is properly configured for conflicting attributes.

Step 6: Execute a manual reconciliation test by navigating to Configuration Management > Identification and Reconciliation > Test Reconciliation and input the affected CI to verify the conflict resolution.

Step 7: Clear any existing reconciliation conflicts by running the 'Reset Reconciliation State' scheduled job or manually updating the cmdb_ci record's reconciliation status to allow fresh processing.

Step 8: Monitor subsequent reconciliation runs through CMDB Dashboard > Reconciliation Status to confirm conflicts are resolved and data sources are properly prioritized.