---
sourceDocument: Brazil ServiceNow AI Platform Capabilities
sourceDocumentLink: https://www.servicenow.com/docs/r/servicenow-platform

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# IRE error messages

# IRE error messages {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of IRE error messages

The Identification and Reconciliation Engine (IRE) in ServiceNow generates various error messages during CI identification and reconciliation processes.
These errors appear in the Identification Logging pane and system logs, helping administrators diagnose and resolve issues related to payload processing, identification rules, duplicate records, and relationships.
Understanding these error messages enables effective troubleshooting and ensures data integrity within the CMDB.
Show full answer Show less  

## Common Error Types and Resolutions

* **Identification Rule Errors:** Errors such as `IDENTIFICATIONRULEMISSING`, `MISSINGMATCHINGATTRIBUTES`, and `NOCLASSNAMEFORINDEPENDENTCI` indicate missing or misconfigured identification rules or attributes. Resolution involves verifying and activating identification rules for the specified tables and ensuring the correct attributes are included.
* **Lookup and Related Rule Errors:** Errors like `IDENTIFICATIONRULEFORLOOKUPMISSING` and `IDENTIFICATIONRULEFORRELATEDITEMMISSING` occur when lookup or related rules are missing for classes referenced in payloads. Administrators should add the corresponding lookup or related entries in the CI Identifier definitions to resolve these.
* **Duplicate Records and Payload Issues:** Errors such as `DUPLICATEPAYLOADRECORDS`, `MULTIPLEDUPLICATERECORDS`, and `DUPLICATERELATIONSHIPTYPES` highlight duplicate entries in payloads or CMDB tables. Resolution requires removing duplicates and reviewing de-duplication tasks.
* **Payload Validation Errors:** Errors like `INVALIDINPUTDATA`, `REQUIREDATTRIBUTEEMPTY`, and JSON parsing errors indicate invalid or missing data in payloads. Resolutions include providing valid sysids, mandatory attribute values, and correctly formatted JSON payloads.
* **Relationship and Metadata Errors:** Issues such as `MISSINGDEPENDENCY`, `METADATARULEMISSING`, and `MULTIPLEDEPENDENCIES` relate to missing or conflicting relationship definitions or metadata rules. Adding appropriate relations and containment/hosting rules in the payload resolves these errors.
* **Lock and Processing Errors:** Errors like `LOCKTIMEOUT` and recursive API calls indicate processing or synchronization issues. Increasing mutex expiration or avoiding recursive API calls are necessary steps.
* **Qualification and Reclassification Errors:** Errors such as `QUALIFICATIONLOOP`, `TYPECONFLICTINQUALIFICATION`, and `RECLASSIFICATIONNOTALLOWED` occur due to loops, multiple qualification paths, or invalid CI reclassification attempts. Removing loops, duplicate paths, or verifying reclassification rules resolves these issues.
* **Data Source Restrictions:** The `INSERTNOTALLOWEDFORSOURCE` error indicates that a configured IRE data source rule blocks insertion of CIs from a specific data source. Adjusting or deleting the relevant data source rule allows insertion or waiting for another permitted source to create the CI.

## Practical Guidance for ServiceNow Customers

* Regularly verify that all necessary identification, lookup, and related rules are configured and active for your CI classes to prevent identification errors.
* Ensure payloads contain all required attributes, valid sysids, and conform to expected JSON formats to avoid processing failures.
* Monitor and resolve duplicate records promptly using de-duplication tasks to maintain CMDB data quality.
* Review and maintain relationship and containment/hosting metadata rules to support accurate dependency mappings.
* Configure system properties such as mutex expiration to optimize synchronization and avoid lock timeouts.
* Validate qualification chains and reclassification rules to prevent loops and invalid classification changes.
* Manage IRE data source rules carefully to control which sources can insert or update CIs, ensuring data integrity from authorized sources only.

Addressing these error messages systematically will help maintain a healthy CMDB, improve identification accuracy, and streamline configuration management processes in ServiceNow.  
The Identification and Reconciliation Engine (IRE) generates the following errors and
messages. Depending on settings, these messages appear in the Identification Logging pane and in
the system logs.
For information about lookup-based CI identification and qualifier chains, see [Create a CI identification rule](https://www.servicenow.com/docs/paokIuIucqW~B7gJNdcX7A "Identification rules are used to uniquely identify CIs in the CMDB, as part of Identification and Reconciliation (IRE) processes. Each CMDB class can be associated with a single identification rule.").  
Note:  
IRE performs an initial verification of a payload before processing identification rules. If IRE detects any duplicate CIs based on any class identifiers, the payload is rejected and processing stops.

For information about CMDB Identification Payload error: "FAILED TRYING TO EXECUTE ON
CONNECTION", see [CMDB Identification Payload error - "Insertion failed with error Error
during insert of cmdb_ci...", where node logs show "FAILED TRYING TO EXECUTE ON
CONNECTION" "Duplicate entry 'XXX' for key 'XXX'"](https://support.servicenow.com/kb_view.do?sysparm_article=KB0812609) knowledge base
article.

## Error- IDENTIFICATION_RULE_MISSING

{#id-engine-error-messages__table_k1v_mml_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Identity Rule Missing for table \[xyz\] | Description: :   Identification rule is missing for a class. Resolution: :   Ensure that there is an identification rule for table \[xyz\], and that the rule is active. |
[ ]

{#id-engine-error-messages__table_k1v_mml_yy}

## MISSING_MATCHING_ATTRIBUTES {#id-engine-error-messages__section_yz3_lbj_h1b}

{#id-engine-error-messages__table_zz3_lbj_h1b__entry__2}

| Message | Description and Resolution |
|-|-|
| In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table \[xyz\]. Add these input values in payload item 'abc' | Description: :   Missing minimum set of values for criterion attributes for an identification rule. Resolution: :   In the payload, add minimum set of values for criterion attributes for CI Identifier for table \[xyz\]. Open the [CI Class Manager](https://www.servicenow.com/docs/paokIuIucqW~B7gJNdcX7A "Identification rules are used to uniquely identify CIs in the CMDB, as part of Identification and Reconciliation (IRE) processes. Each CMDB class can be associated with a single identification rule."), click Hierarchy and select the \[xyz\] class. Check the identification rule and the identifier entries for table \[xyz\]. |
[ ]

{#id-engine-error-messages__table_zz3_lbj_h1b}

## Error- NO_CLASS_NAME_FOR_INDEPENDENT_CI

{#id-engine-error-messages__table_kyc_nml_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Cannot have 'sys_class_name' as a key field in an Independent Identity Rule on 'xyz' | Description: :   The class attribute was added to the CI identifier which is not supported. Resolution: :   Remove the class attribute from CI Identifier for table \[xyz\]. |
[ ]

{#id-engine-error-messages__table_kyc_nml_yy}

## Error- IDENTIFICATION_RULE_FOR_LOOKUP_MISSING

{#id-engine-error-messages__table_cjk_nml_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Identity Rule for table \[xyz\] missing Lookup Rule for class \[abc\] | Description: :   The payload has a lookup class name, but the corresponding lookup rule is missing. Resolution: :   Add lookup identifier entry with \[Search on table\] as \[abc\] for CI Identifier for table \[xyz\]. For more information about this error message, see [Identification error "Identity Rule for table \[cmdb_ci_table_name\] missing Lookup Rule for class \[table_name\]" \[KB0786444\]](https://support.servicenow.com/kb_view_customer.do?sysparm_article=KB0786444). |
[ ]

{#id-engine-error-messages__table_cjk_nml_yy}

## Error- IDENTIFICATION_RULE_FOR_RELATED_ITEM_MISSING

{#id-engine-error-messages__table_zhw_3nl_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Identity Rule for table \[xyz\] missing Related Rule for class \[abc\] | Description: :   The payload has a related class name, but the corresponding related rule is missing. Resolution: :   Add related entry with \[Related table\] as \[abc\] within CI Identifier for table \[xyz\]. |
[ ]

{#id-engine-error-messages__table_zhw_3nl_yy}

## Error- NO_LOOKUP_RULES_FOR_DEPENDENT_CI

{#id-engine-error-messages__table_mxb_jnl_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Cannot have Lookup Rule for a Dependent Identity Rule on 'xyz' | Description: :   Cannot have Lookup Rule for a Dependent Identity Rule. Resolution: :   Remove lookup identifier entry from dependent CI Identifier for table \[xyz\]. |
[ ]

{#id-engine-error-messages__table_mxb_jnl_yy}

## Error- INVALID_INPUT_DATA

{#id-engine-error-messages__table_bff_jnl_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Found invalid sys_id in payload. No record with sys_id \[xyz\] exist in table \[abc\] or is a duplicate record with \[duplicate_of\] field set to a main CI | Description: :   The payload has a reference to an invalid sys_id. Resolution: :   Remove the referenced sys_id, or provide a valid sys_id. |
| In payload no data source exist. You need to provide choice value from choice field \[discovery_source\] in table \[cmdb_ci\] | Description: :   In payload no data source exists. Resolution: :   In the payload, provide a valid choice value from choice field \[discovery_source\] from table \[cmdb_ci\]. |
| In payload invalid data source \[xyz\] exist. You need to provide a valid choice value from field \[discovery_source\] in table \[cmdb_ci\] | Description: :   The payload contains an invalid data source. Resolution: :   In the payload, provide a valid choice value from choice field \[discovery_source\] from table \[cmdb_ci\]. |
| No such relationship with name \[xyz\] exist in table \[cmdb_rel_type\]. If out-of-box relationship for \[xyz\] has been removed or renamed, it should be restored | Description: :   The payload is referencing a relationship that does not exist in the \[cmdb_rel_type\] table. Resolution: :   Verify that the reference to the relationship is accurate. Or, if it is a new relationship, add it to the \[cmdb_rel_type\] table. Or, If out-of-box relationship for \[xyz\] has been removed or renamed, restore it. |
| Payload relations 'xyz' has invalid parent record index: \[0\] | Description: :   Payload references invalid parent indexes. Resolution: :   Check payload indexes and ensure that they are all valid. |
| Payload relations 'xyz' has invalid child record index: \[0\] | Description: :   Payload references invalid child indexes. Resolution: :   Check payload indexes and ensure that they are all valid. |
[ ]

{#id-engine-error-messages__table_bff_jnl_yy}

## Error- DUPLICATE_RELATIONSHIP_TYPES

{#id-engine-error-messages__table_tbl_jnl_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Duplicate relationship type records exists with name \[xyz\] in table \[cmdb_rel_type\] having sys_ids: \[abc\] | Description: :   There are duplicate records in the \[rel_ci_type\] table for the relationship. Resolution: :   Remove the duplicate records. |
[ ]

{#id-engine-error-messages__table_tbl_jnl_yy}

## Error- DUPLICATE_PAYLOAD_RECORDS

{#id-engine-error-messages__table_jww_cpl_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Found duplicate items in the payload (index 0 and 1), using className \[xyz\] and fields \[abc\]. Remove duplicate items from payload | Description: :   The payload contains two items whose criterion attributes have identical values. Resolution: :   Remove one of the duplicate items. |
[ ]

{#id-engine-error-messages__table_jww_cpl_yy}

## Error- LOCK_TIMEOUT

{#id-engine-error-messages__table_y2j_2pl_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Failed to acquire synchronization lock for xyz | Description: :   Failed to acquire the system mutex lock. Resolution: :   Increase the mutex expiration time by adding the system property glide.identification_engine.mutex_expiration_time and setting to an integer value that is greater than the default value (15 min). |
[ ]

{#id-engine-error-messages__table_y2j_2pl_yy}

## Error- MULTIPLE_DUPLICATE_RECORDS

{#id-engine-error-messages__table_zjm_2pl_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Found duplicate records in table \[xyz\] using fields \[abc\] | Description: :   Found duplicate records in the specified table. Resolution: :   Fix the duplicate records found by the identification engine. Check de-duplication tasks for information about all duplicates. |
[ ]

{#id-engine-error-messages__table_zjm_2pl_yy}

## Error- REQUIRED_ATTRIBUTE_EMPTY

{#id-engine-error-messages__table_apq_2pl_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Missing mandatory field \[xyz\] in table \[abc\]. Add input value for mandatory field in payload | Description: :   A required attribute is missing in the payload. Resolution: :   In the payload, add input value for mandatory field \[xyz\] in table \[abc\]. |
[ ]

{#id-engine-error-messages__table_apq_2pl_yy}

## Error- MISSING_DEPENDENCY

{#id-engine-error-messages__table_wgv_2ql_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| In payload no relations defined for dependent class \[xyz\] that matches any containment/hosting rules: \[abc\]. Add appropriate relations in payload for 'def' | Description: :   No relations defined for the dependent class that matches any of its metadata rules. Resolution: :   In payload add appropriate relations for dependent class \[xyz\] that matches any containment/hosting rules: \[abc\]. |
[ ]

{#id-engine-error-messages__table_wgv_2ql_yy}

## Error- METADATA_RULE_MISSING {#id-engine-error-messages__section_d5y_pf2_5z}

{#id-engine-error-messages__table_e5y_pf2_5z__entry__2}

| Message | Description and Resolution |
|-|-|
| No containment or hosting rules defined for dependent class \[xyz\]. Add containment/hosting rules for 'abc' | Description: :   There are no containment or hosting rules defined for dependent class. Resolution: :   Add containment or hosting rules for dependent class \[xyz\]. |
[ ]

{#id-engine-error-messages__table_e5y_pf2_5z}

## Error- MULTIPLE_DEPENDENCIES

{#id-engine-error-messages__table_c2x_fql_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Found multiple dependent relation items \[xyz\] and \[abc\] in payload | Description: :   Multiple dependent relation items exist. Resolution: :   Remove one of the multiple dependent relation items \[xyz\] or \[abc\]. |
| Multiple paths leading to the same destination: xyz -\> abc | Description: :   Multiple paths leading to the same destination. Resolution: :   Remove duplicate relationship/qualifier chains that might exists between xyz -\> abc. |
[ ]

{#id-engine-error-messages__table_c2x_fql_yy}

## Error- ABANDONED

{#id-engine-error-messages__table_w1c_gql_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Abandoning processing payload item 'xyz', since its depends on payload item 'abc' has errors | Description: :   Dependent payload item has errors, so abandoning processing. Resolution: :   Resolve the error on the dependent payload item 'abc'. |
| Can't find matched record with sys_id \[xyz\] in table \[abc\] | Description: :   Matched sys_id does not exist in the corresponding table. Resolution: :   Check in table \[abc\] whether matched record is a valid record based on input payload. |
| Identification engine API got called recursively, aborting... | Description: :   The Identification engine API was called recursively. Resolution: :   Avoid calling the Identification engine API recursively. |
| Detected error while processing payload from xyz | Description: :   Error occurred during processing payload. Resolution: :   Resolve all errors mentioned in the output payload from xyz. |
| While processing relations encountered errors in payload item: xyz | Description: :   Payload item has errors. Resolution: :   Resolve errors in payload item 'xyz'. |
| Error occurred during parsing input json payload: xyz | Description: :   Error occurred during parsing JSON payload. Resolution: :   Ensure that input JSON payload has correct JSON format. |
[ ]

{#id-engine-error-messages__table_w1c_gql_yy}

## Error- MULTI_MATCH

{#id-engine-error-messages__table_xwf_gql_yy__entry__2}

| Message | Description and Resolution |
|-|-|
| Duplicate dependent records found having relationship \[xyz\] with same CI (className:\[abc\], sysId:\[def\]) | Description: :   Found duplicate dependent CIs. Resolution: :   Check de-duplication tasks for information about all duplicates, and then delete duplicate records. |
| Found multiple relations between payload items: 'xyz' and 'abc' | Description: :   Found multiple relations between payload items. Resolution: :   Check for duplicate relationship chains and qualifier chains that might exist. |
| Found duplicate records in lookup table \[xyz\] using fields \[abc\] and reference field \[def\] | Description: :   Found duplicate records in lookup table. Resolution: :   Check de-duplication tasks for information about all duplicates, and then delete duplicate records. |
[ ]

{#id-engine-error-messages__table_xwf_gql_yy}

## Error- QUALIFICATION_LOOP {#id-engine-error-messages__section_fm3_knp_4z}

{#id-engine-error-messages__table_gm3_knp_4z__entry__2}

| Message | Description and Resolution |
|-|-|
| Qualification chain has loop that contains relation 'xyz' | Description: :   Qualification chain has a loop. Resolution: :   Remove the loop from the qualification chain with relation 'xyz'. |
[ ]

{#id-engine-error-messages__table_gm3_knp_4z}

## Error- TYPE_CONFLICT_IN_QUALIFICATION {#id-engine-error-messages__section_hzs_vnp_4z}

{#id-engine-error-messages__table_izs_vnp_4z__entry__2}

| Message | Description and Resolution |
|-|-|
| Invalid payload, qualification chain has multiple possible paths for payload items: 'xyz' and 'abc' | Description: :   Multiple qualification paths found. Resolution: :   Remove multiple possible qualification paths between items 'xyz' and 'abc'. |
[ ]

{#id-engine-error-messages__table_izs_vnp_4z}

## Error- RECLASSIFICATION_NOT_ALLOWED {#id-engine-error-messages__section_oj4_hsp_4z}

{#id-engine-error-messages__table_pj4_hsp_4z__entry__2}

| Message | Description and Resolution |
|-|-|
| CI Reclassification not allowed from class: \[xyz\] to \[abc\] | Description: :   CI reclassification not allowed. Resolution: :   Check reclassification tasks for information about reclassification, and check if reclassification from class: \[xyz\] to \[abc\] is valid. |
[ ]

{#id-engine-error-messages__table_pj4_hsp_4z}

## Error- DUPLICATE_RELATED_PAYLOAD {#id-engine-error-messages__section_h15_qyp_4z}

{#id-engine-error-messages__table_i15_qyp_4z__entry__2}

| Message | Description and Resolution |
|-|-|
| Found duplicate Related items (0 and 1) in the payload index 1 using fields xyz | Description: :   Duplicate Related items present. Resolution: :   Remove one of the duplicate related items present in the payload. |
[ ]

{#id-engine-error-messages__table_i15_qyp_4z}

## Error- DUPLICATE_LOOKUP_PAYLOAD {#id-engine-error-messages__section_v3h_typ_4z}

{#id-engine-error-messages__table_w3h_typ_4z__entry__2}

| Message | Description and Resolution |
|-|-|
| Found duplicate Lookup items (0 and 1) in the payload index 1 using fields xyz | Description: :   Duplicate lookup items present. Resolution: :   Remove one of the duplicate lookup items present in the payload. |
[ ]

{#id-engine-error-messages__table_w3h_typ_4z}

## INSERT_NOT_ALLOWED_FOR_SOURCE {#id-engine-error-messages__section_clz_lcg_kjb}

{#id-engine-error-messages__table_dlz_lcg_kjb__entry__2}

| Message | Description and Resolution |
|-|-|
| Insert into \[xyz\] is blocked for data source \[abc\] by IRE data source rule | Description: :   An [IRE data source rule](https://www.servicenow.com/docs/VwgNd9UMN3Mh~b5kqOzH9w "When using Identification and Reconciliation Engine (IRE), you can prevent a specific discovery (data) source from inserting new CIs for a specific class. Create IRE data source rules for discovery sources that you don't trust in creating CIs but continue to trust in updating those CIs that exist.") is configured to prevent data source \[abc\] from inserting CIs of the \[xyz\] class. Resolution: :   Delete or update the appropriate IRE data source rule to let data source \[abc\] insert CIs of the \[xyz\] class. Or, wait for another permitted data source to create the same CI. |
[ ]

{#id-engine-error-messages__table_dlz_lcg_kjb}