Discovery Failed Due to MISSING_MATCHING_ATTRIBUTES in PayloadDescriptionDiscovery failed due the below error in the Discovery Pattern Logs. Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error: commit failed or was not attempted due to other errors.,Insertion failed with error 1. Copy the Input HorizontalDiscoveryProbe Payload 2. Check the Payload in the Identification Simulation and will observe the below error MISSING_MATCHING_ATTRIBUTES In payload missing minimum set of input values for criterion (matching) attributes from identify rule for table [cmdb_ci_print_queue]. Add these input values in payload item Debug : identification_engine : addAttempt [{"className":"cmdb_ci_network_adapter","values":{"dhcp_enabled":"False","short_description":"vmxnet3 Ethernet Adapter","discovery_source":"ServiceNow","install_status":"1","netmask":"255.255.255.224","mac_address":"00:50:56:AF:BE:57","name":"Ethernet0","ip_address":"10.48.130.193","ip_default_gateway":"10.48.130.222","sys_class_name":"cmdb_ci_network_adapter","manufacturer":"VMware, Inc."},"internal_id":"8a050a6d9d54c150d4185b6574e5dbd4","sys_object_source_info":{"source_name":"ServiceNow"},"settings":{},"sys_ire_info":{"ire_received_time":"2021-12-08 07:30:53"}}] - [sys_object_source] SKIPPED 3. Navigate to CI Identifiers and search for Print Queue identifier >> Open the Record. Release or EnvironmentQuebec Cause1. In the Identifier entries, the OOB Criterion Attributes will check for Name, Ip_Address. 2. Here, In this case user has modified the OOB Criterion Attributes by adding Serial Number. 3. End User is discovering a VM server and it does not have a serial number and at the Print Queue step it was checking for a serial number 4. The discovery is failing because it was unable to capture serial number information. ResolutionMade the Print Queue Criterion Attributes to OOB by removing Serial Number >> ran the discovery and it was working fine.Additional InformationHow to use Identification Simulator, Please click here