BMC Discovery synchronization to Servicenow SummaryBMC Helix discovery throwing IRE errors Error identification_engine : logId:[499b666a870a] Output = {"items":[{"className":"cmdb_ci_vcenter","sysId":"Unknown","identifierEntrySysId":"Unknown","errors":[{"error":"MISSING_DEPENDENCY","message":"In payload no relations defined for dependent class [cmdb_ci_vcenter] that matches any containment/hosting rules: [cmdb_ci_appl >> Runs >> cmdb_ci_logical_datacenter,cmdb_ci_appl >> Runs >> cmdb_ci_cluster,cmdb_ci_appl >> Runs on >> cmdb_ci_hardware]. Add appropriate relations in payload for '{\"className\":\"cmdb_ci_vcenter\",\"values\":{\"running_process_key_parameters\":\"VMware vCenter Server/9yJArHo2pLlgjNxp/wRaLw==\",\"discovery_source\":\"BMC Discovery\",\"install_status\":\"1\",\"name\":\"VMware vCenter Server 7.0 on in14svc01.ap.mt.mtnet\",\"correlation_id\":\"VMware vCenter Server/9yJArHo2pLlgjNxp/wRaLw==#cmdb_ci_vcenter\",\"fullname\":\"VMware vCenter Server 7.0 on in14svc01.ap.mt.mtnet 7.0.2.18455184\",\"sys_class_name\":\"cmdb_ci_vcenter\"},\"internal_id\":\"c99b666a7a0aa95014a2d59627f4fd6d\",\"sys_object_source_info\":{},\"settings\":{},\"sys_ire_info\":{},\"display_values\":{}}'"},{"error":"ABANDONED","message":"Too many other errors"}],"identificationAttempts":[{"info":"sys_object_source SKIPPED","attemptResult":"SKIPPED","identifierName":"","attributes":["source_name","source_native_key"],"hybridEntryCiAttributes":[],"searchOnTable":"sys_object_source"}],"info":[],"errorCount":2,"warningCount":0,"inputIndices":[0],"mergedPayloadIds":[],"markers":[]}],"additionalCommittedItems":[],"relations":[],"additionalCommittedRelations":[]}: no thrown error com.glide.ui.ServletErrorListener Ask customer to do below: 1. Regarding ServiceNow and BMC Discovery integration please reach out to BMC to understand why the payload that is sent to the instance is different from their personal instance as trying to capture the payload generated at the source might help narrow down the cause.2. Servicenow is not initiating the BMC discovery and it is only being used to store the data. BMC discovery is responsible for querying the data.Recommend to reach out to BMC team to understand why the remaining installs are missing and data is not collected.glide.rest.debug can be used to show the incoming payload at ServiceNow. Trying to capture the payload generated at the source might help narrow down the cause for missing the installs on the table.3. OOTB we use traditional discovery to update the software install table.https://docs.bmc.com/docs/discovery/daas/preparing-servicenow-cmdb-for-synchronization-906457191.htmlhttps://docs.bmc.com/docs/discovery/120/preparing-servicenow-cmdb-for-synchronization-911458812.html4. Kindly check if any customisations done & revert back to OOB and then make the required changes and rediscover.