---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Find the cause of a sensor error message

# Find the cause of a sensor error message {#ariaid-title1}

* Release version: Yokohama
* 
* Updated June 5, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Use this procedure to identify a Discovery sensor error.

## Before you begin

Role required: sn_cloud_ops_ws.cloud_ops_admin or admin

## About this task

This process requires that you identify the following:

* The error.
* The name of the sensor where the error occurred.
* The datestamp of the error.
* The associated stack trace of the error.
{#t_FindTheCauseOfASensorErrorMessage__ul_o3w_3ff_ss}

## Procedure

1. Depending on the application you are using, do one of the following:
   * To view the Discovery Log in Cloud Discovery Workspace, navigate to Cloud Discovery WorkspaceCloud DiscoveryDiscovery Log.
   * To view the Discovery Log in Discovery, navigate to AllDiscoveryDiscovery Log.
   {#t_FindTheCauseOfASensorErrorMessage__choices_mm2_51k_jsb}
2. To find the error, filter on the Level name of Error.  
   If you are using Discovery, you can also view the error and the date stamp in the Error Report. The report is available on the Discovery dashboard.
3. Note the Created field of the error record.  
   This timestamp is used to find the proper stack trace.
4. Note the Short Message field of the error record.  
   This field shows the name of the sensor where the error has occurred.
5. To find the stack trace, navigate to System LogsErrors.
6. Search for the date and time that matches the value in the Created field of the error record in the Discovery Log.
7. The Message field of that entry contains the full stack trace of the error.  
   The stack trace contains the error message, the sys_id of the script, and the line number where the error has occurred.
8. After determining the error details, you can fix the JavaScript file.
**Related tasks**   

* [Find the cause of a "No Sensor Defined" error message](https://servicenow-prod.fluidtopics.net/NZ55aWZ6S7D67~BW_W1XbA "Every active probe looks for a corresponding sensor to process the data that is collected by the probe. The \"No Sensors Defined\" message indicates that the corresponding sensor for the probe is missing or inactive.")
* [Fix the cause of a sensor error message](https://servicenow-prod.fluidtopics.net/P0bMu5sNRxNBI83z1m~NQA "To fix a Discovery sensor error message, you must fix the JavaScript file containing the code that generated the error.")
* [Find the cause of a "Probe not found" error](https://servicenow-prod.fluidtopics.net/_iB3679AcTS~ZMLucLmRFg "Verify the correct sys_id of the probe associated with the probe parameter in the payload of the ECC Queue input record.")

*[\>]: and then