Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform capabilities
Table of Contents
Choose your release version
    Home Orlando Now Platform Capabilities Now Platform capabilities Configuration Management Database CMDB Identification and Reconciliation Generate and simulate payload execution using identification simulation

    Generate and simulate payload execution using identification simulation

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Generate and simulate payload execution using identification simulation

    Identification simulation is a central location for automatically constructing a payload that is guaranteed to be complete and valid. You can then simulate the processing of the payload by the identification and reconciliation engine (IRE) and examine the results before actually submitting it for execution by IRE.

    Use identification simulation to construct an input payload, and simulate processing of the payload by IRE. You can then examine the results, adjust identification rules if needed, and re-run the simulation of the updated payload.

    Use the identification simulation to:
    • Automatically construct input payload that is based on existing identification rules, hosting and containment rules.
    • Simulate execution of a payload (automatically constructed by identification simulation, or manually created).
    • Browse payload output and execution log messages for a simulated run.
    Note: Identification simulation does not commit any updates to the CMDB.

    Automatically generate payload using identification simulation

    Use identification simulation to automatically construct an input payload for a specified class. The constructed payload is complete with any required dependent CIs, correctly structured, and syntactically valid for processing by the identification and reconciliation engine (IRE).

    Before you begin

    Role required: admin

    About this task

    The payload that is constructed during identification simulation is for the specified class. For a dependent CI class, you will be prompted for information about all dependencies. After you provide the required details, identification simulation constructs the payload based on your input.

    Procedure

    1. Navigate to Configuration > Identification/Reconciliation, and click Identification Simulation.
    2. In the Start with CI Class box click Start.
    3. On the Payload Information form, in the Data source field, select the data source that is associated with this class update.
      For the ServiceNow Discovery data source, select ServiceNow.
    4. Select the Class in the payload.
      1. In the Criterion Attributes area select the CI identifier attributes and then specify the values that uniquely identify a CI.
      2. In the Additional Attributes area specify attributes and values that matching CIs will be updated with.
    5. For dependent CIs associated with dependent identification rules, fill out the Criterion Attributes and Additional Attributes sections in all Container level sections that display.
    6. Click Generate Script. If any errors indicate that there are missing fields, fill in the missing fields and then click Generate Script again.

    What to do next

    • Click Run Simulation to simulate processing of the payload by IRE.
    • Examine the results of the simulation, fine-tune the payload as needed, and combine with other payloads for other classes as desired. After finalizing the payload, use the createOrUpdateCI() API to execute the payload by IRE which will result in actual updates to the CMDB.
    • Click Copy Script to copy the JSON script into the clipboard. You can then paste that script into a third party software or to another screen of the identification simulation.

    Simulate payload processing using identification simulation

    Use identification simulation to simulate the identification and reconciliation engine (IRE) process of CI identification for an input payload. Provide a valid payload, which was constructed using identification simulation or that was created manually.

    Before you begin

    Role required: admin

    Procedure

    1. Navigate to Configuration > Identification/Reconciliation, and click Identification Simulation.
    2. (Optional) To run a simulation of an existing payload:
      1. Click Start in the Start with Existing Payload tile.
      2. In the Data source field, select the data source that is associated with this class update.
      3. Paste the JSON payload into the empty canvas.
    3. (Optional) To construct a new payload click Start in the Start with CI Class tile. See Automatically generate payload using identification simulation for more information.
    4. Click Run Simulation to simulate processing of the payload by IRE.

    What to do next

    1. Examine the results of the simulation in the results pane, and fine-tune the payload as needed:
      1. Click Run #1 to display the Context ID and the Run ID of the simulated run.
      2. Click the drop down arrow next to Run #1 to display additional details.
        • Input: Displays the payload for the simulation.
        • Logs: Displays all the logged messages that IRE generated while simulating processing of the payload, according to the specified logging level.
        • Output: Displays the output payload returned by IRE.
    2. After finalizing the payload, use the createOrUpdateCI() API to execute the payload by IRE which will result in actual updates to the CMDB.

    Set logging level for identification simulation

    Identification simulation logs each step of a simulated payload processing. You can then examine these run logs to determine if a payload was processed as expected, and if identification rules are effective. You can adjust the level of logging so it is helpful, and so that the amount of messages is not excessive or insufficient.

    Before you begin

    Role required: admin

    Procedure

    1. Navigate to Configuration > Identification/Reconciliation, and click Identification Simulation.
    2. Click the Settings icon.
    3. Select logging level for the identification and reconciliation engine (IRE) under IE Log Level and for the service cache under Service Cache Log Level.
      The logging levels are displayed in ascending order, from the minimum level to the maximum level of logging.
    4. Click on the Settings icon again to close the Settings dialog box.

    Examine run logs

    Identification simulation provides run logs which are generated by Identification and Reconciliation Engine (IRE). You can access these run logs for payload runs, to examine results and for debugging purposes. IRE payload output logs appear in a user friendly format on a central page.

    Before you begin

    Role required: admin

    About this task

    Also, internal applications that use IRE (such as Discovery) can call an internal API to provide a URL to viewing IRE run logs.

    Logging is in the context of a specific run of the identification engine, and you can filter the log list by a specific data source and time range. Up to 1000 run logs that are up to 2 months old are listed, grouped by Context IDs, and run times. You can use the glide.identification_logs.max_run_ids property to modify the 1000 limit.

    You can control the logging level by using the glide.discovery.identification.log_level Discovery system property and setting the value to one of the following:
    • Info
    • Warn
    • Error
    • Debug
    • DebugVerbose
    • DebugObnoxious
    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.

    Procedure

    1. Navigate to Configuration > Identification/Reconciliation > Identification Logs.
    2. Filter the runs list as follows:
      1. Source: Select the data source for which to display run logs.
      2. Time Range: Specify a time range for which to display run logs.
      The Runs list displays all runs for the specified data source, during the specified time range.
    3. In the Runs list, click a Run # to display its Context ID and Run ID.
      A unique Context ID is associated with each specific payload that is run. Each run of that payload, is associated with a unique Run ID. A single Context ID for a payload that is run multiple times is associated with multiple Run IDs.
    4. Click the drop down arrow for a Run # to display additional details.
      • Input: Displays the payload for the run.
      • Logs: Displays all the logged messages that the identification engine generated while running the payload, according to the specified logging level.
      • Output: Displays the output payload returned by the identification engine.

    IRE error messages

    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 or edit a CI 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.

    Error: IDENTIFICATION_RULE_MISSING

    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.

    MISSING_MATCHING_ATTRIBUTES

    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, click Hierarchy and select the [xyz class. Check the identification rule and the identifier entries for table [xyz.

    Error: NO_CLASS_NAME_FOR_INDEPENDENT_CI

    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].

    Error: IDENTIFICATION_RULE_FOR_LOOKUP_MISSING

    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].

    Error: IDENTIFICATION_RULE_FOR_RELATED_ITEM_MISSING

    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].

    Error: NO_LOOKUP_RULES_FOR_DEPENDENT_CI

    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].

    Error: INVALID_INPUT_DATA

    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 master 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.

    Error: DUPLICATE_RELATIONSHIP_TYPES

    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.

    Error: DUPLICATE_PAYLOAD_RECORDS

    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.

    Error: LOCK_TIMEOUT

    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).

    Error: MULTIPLE_DUPLICATE_RECORDS

    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.

    Error: REQUIRED_ATTRIBUTE_EMPTY

    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].

    Error: MISSING_DEPENDENCY

    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].

    Error: METADATA_RULE_MISSING

    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].

    Error: MULTIPLE_DEPENDENCIES

    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.

    Error: ABANDONED

    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.

    Error: MULTI_MATCH

    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.

    Error: QUALIFICATION_LOOP

    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'.

    Error: TYPE_CONFLICT_IN_QUALIFICATION

    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'.

    Error: RECLASSIFICATION_NOT_ALLOWED

    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.

    Error: DUPLICATE_RELATED_PAYLOAD

    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.

    Error: DUPLICATE_LOOKUP_PAYLOAD

    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.

    INSERT_NOT_ALLOWED_FOR_SOURCE

    Message Description and Resolution
    Insert into [xyz] is blocked for data source [abc] by IRE data source rule
    Description:
    An IRE data source rule 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.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Generate and simulate payload execution using identification simulation

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Generate and simulate payload execution using identification simulation

      Identification simulation is a central location for automatically constructing a payload that is guaranteed to be complete and valid. You can then simulate the processing of the payload by the identification and reconciliation engine (IRE) and examine the results before actually submitting it for execution by IRE.

      Use identification simulation to construct an input payload, and simulate processing of the payload by IRE. You can then examine the results, adjust identification rules if needed, and re-run the simulation of the updated payload.

      Use the identification simulation to:
      • Automatically construct input payload that is based on existing identification rules, hosting and containment rules.
      • Simulate execution of a payload (automatically constructed by identification simulation, or manually created).
      • Browse payload output and execution log messages for a simulated run.
      Note: Identification simulation does not commit any updates to the CMDB.

      Automatically generate payload using identification simulation

      Use identification simulation to automatically construct an input payload for a specified class. The constructed payload is complete with any required dependent CIs, correctly structured, and syntactically valid for processing by the identification and reconciliation engine (IRE).

      Before you begin

      Role required: admin

      About this task

      The payload that is constructed during identification simulation is for the specified class. For a dependent CI class, you will be prompted for information about all dependencies. After you provide the required details, identification simulation constructs the payload based on your input.

      Procedure

      1. Navigate to Configuration > Identification/Reconciliation, and click Identification Simulation.
      2. In the Start with CI Class box click Start.
      3. On the Payload Information form, in the Data source field, select the data source that is associated with this class update.
        For the ServiceNow Discovery data source, select ServiceNow.
      4. Select the Class in the payload.
        1. In the Criterion Attributes area select the CI identifier attributes and then specify the values that uniquely identify a CI.
        2. In the Additional Attributes area specify attributes and values that matching CIs will be updated with.
      5. For dependent CIs associated with dependent identification rules, fill out the Criterion Attributes and Additional Attributes sections in all Container level sections that display.
      6. Click Generate Script. If any errors indicate that there are missing fields, fill in the missing fields and then click Generate Script again.

      What to do next

      • Click Run Simulation to simulate processing of the payload by IRE.
      • Examine the results of the simulation, fine-tune the payload as needed, and combine with other payloads for other classes as desired. After finalizing the payload, use the createOrUpdateCI() API to execute the payload by IRE which will result in actual updates to the CMDB.
      • Click Copy Script to copy the JSON script into the clipboard. You can then paste that script into a third party software or to another screen of the identification simulation.

      Simulate payload processing using identification simulation

      Use identification simulation to simulate the identification and reconciliation engine (IRE) process of CI identification for an input payload. Provide a valid payload, which was constructed using identification simulation or that was created manually.

      Before you begin

      Role required: admin

      Procedure

      1. Navigate to Configuration > Identification/Reconciliation, and click Identification Simulation.
      2. (Optional) To run a simulation of an existing payload:
        1. Click Start in the Start with Existing Payload tile.
        2. In the Data source field, select the data source that is associated with this class update.
        3. Paste the JSON payload into the empty canvas.
      3. (Optional) To construct a new payload click Start in the Start with CI Class tile. See Automatically generate payload using identification simulation for more information.
      4. Click Run Simulation to simulate processing of the payload by IRE.

      What to do next

      1. Examine the results of the simulation in the results pane, and fine-tune the payload as needed:
        1. Click Run #1 to display the Context ID and the Run ID of the simulated run.
        2. Click the drop down arrow next to Run #1 to display additional details.
          • Input: Displays the payload for the simulation.
          • Logs: Displays all the logged messages that IRE generated while simulating processing of the payload, according to the specified logging level.
          • Output: Displays the output payload returned by IRE.
      2. After finalizing the payload, use the createOrUpdateCI() API to execute the payload by IRE which will result in actual updates to the CMDB.

      Set logging level for identification simulation

      Identification simulation logs each step of a simulated payload processing. You can then examine these run logs to determine if a payload was processed as expected, and if identification rules are effective. You can adjust the level of logging so it is helpful, and so that the amount of messages is not excessive or insufficient.

      Before you begin

      Role required: admin

      Procedure

      1. Navigate to Configuration > Identification/Reconciliation, and click Identification Simulation.
      2. Click the Settings icon.
      3. Select logging level for the identification and reconciliation engine (IRE) under IE Log Level and for the service cache under Service Cache Log Level.
        The logging levels are displayed in ascending order, from the minimum level to the maximum level of logging.
      4. Click on the Settings icon again to close the Settings dialog box.

      Examine run logs

      Identification simulation provides run logs which are generated by Identification and Reconciliation Engine (IRE). You can access these run logs for payload runs, to examine results and for debugging purposes. IRE payload output logs appear in a user friendly format on a central page.

      Before you begin

      Role required: admin

      About this task

      Also, internal applications that use IRE (such as Discovery) can call an internal API to provide a URL to viewing IRE run logs.

      Logging is in the context of a specific run of the identification engine, and you can filter the log list by a specific data source and time range. Up to 1000 run logs that are up to 2 months old are listed, grouped by Context IDs, and run times. You can use the glide.identification_logs.max_run_ids property to modify the 1000 limit.

      You can control the logging level by using the glide.discovery.identification.log_level Discovery system property and setting the value to one of the following:
      • Info
      • Warn
      • Error
      • Debug
      • DebugVerbose
      • DebugObnoxious
      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.

      Procedure

      1. Navigate to Configuration > Identification/Reconciliation > Identification Logs.
      2. Filter the runs list as follows:
        1. Source: Select the data source for which to display run logs.
        2. Time Range: Specify a time range for which to display run logs.
        The Runs list displays all runs for the specified data source, during the specified time range.
      3. In the Runs list, click a Run # to display its Context ID and Run ID.
        A unique Context ID is associated with each specific payload that is run. Each run of that payload, is associated with a unique Run ID. A single Context ID for a payload that is run multiple times is associated with multiple Run IDs.
      4. Click the drop down arrow for a Run # to display additional details.
        • Input: Displays the payload for the run.
        • Logs: Displays all the logged messages that the identification engine generated while running the payload, according to the specified logging level.
        • Output: Displays the output payload returned by the identification engine.

      IRE error messages

      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 or edit a CI 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.

      Error: IDENTIFICATION_RULE_MISSING

      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.

      MISSING_MATCHING_ATTRIBUTES

      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, click Hierarchy and select the [xyz class. Check the identification rule and the identifier entries for table [xyz.

      Error: NO_CLASS_NAME_FOR_INDEPENDENT_CI

      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].

      Error: IDENTIFICATION_RULE_FOR_LOOKUP_MISSING

      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].

      Error: IDENTIFICATION_RULE_FOR_RELATED_ITEM_MISSING

      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].

      Error: NO_LOOKUP_RULES_FOR_DEPENDENT_CI

      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].

      Error: INVALID_INPUT_DATA

      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 master 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.

      Error: DUPLICATE_RELATIONSHIP_TYPES

      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.

      Error: DUPLICATE_PAYLOAD_RECORDS

      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.

      Error: LOCK_TIMEOUT

      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).

      Error: MULTIPLE_DUPLICATE_RECORDS

      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.

      Error: REQUIRED_ATTRIBUTE_EMPTY

      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].

      Error: MISSING_DEPENDENCY

      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].

      Error: METADATA_RULE_MISSING

      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].

      Error: MULTIPLE_DEPENDENCIES

      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.

      Error: ABANDONED

      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.

      Error: MULTI_MATCH

      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.

      Error: QUALIFICATION_LOOP

      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'.

      Error: TYPE_CONFLICT_IN_QUALIFICATION

      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'.

      Error: RECLASSIFICATION_NOT_ALLOWED

      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.

      Error: DUPLICATE_RELATED_PAYLOAD

      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.

      Error: DUPLICATE_LOOKUP_PAYLOAD

      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.

      INSERT_NOT_ALLOWED_FOR_SOURCE

      Message Description and Resolution
      Insert into [xyz] is blocked for data source [abc] by IRE data source rule
      Description:
      An IRE data source rule 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.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login