ASYNC: Discovery - Sensors jobs log false "WARNING *** WARNING *** Get for non-existent record: discovery_status:, initializing" for non-Discovery ECC Queue inputsDescriptionASYNC: Discovery - Sensors jobs will spam the instance app node localhost log with false warnings for discovery_status records:WARNING *** WARNING *** Get for non-existent record: discovery_status:<some value>, initializing This is due to the sensor running for non-Discovery ecc queue input records (such as Orchestration, REST/SOAP, JDBC, LDAP etc.), and using .get() as a way of checking if the agent_correlator field value is a discovery_status record. As expected for gliderecord get(), if there is no match, a new gliderecord is initialized and the WARNING logged. A different technique to check needs implementing. The fix for PRB1113671 did not resolve this.Steps to Reproduce Install Discovery or Service Mapping, plus various other integrations on an instance, such as Orchestration, REST/SOAP, JDBC, LDAP etc, where an agent_correlator value is populated in the ecc_queue output.Check the app node localhost logs for "ASYNC: Discovery - Sensors" worker threads, and you will see the logs spammed with thousands of messages like this for ecc queue inputs that have nothing to do with Discovery:WARNING *** WARNING *** Get for non-existent record: discovery_status:6837f06bdbcd4010cb72c7ec0b9619c9, initializingWorkaroundThis problem is currently under review. You can contact ServiceNow Technical Support or subscribe to this Known Error article by clicking the Subscribe button at the top right of this form to be notified when more information will become available. Unless the error is from processing an ecc_queue input for a Discovery job, which may be possible to confirm from other log entries for the same transaction, which may also refer to the probe name or ecc_queue sys_id, this warning can be ignored.Related Problem: PRB1435362