No sensors defined rest message
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-16-2025 01:24 AM
Hello all,
I marked "Use MID server" for one of my HTTP methods to test the mid server i deployed but i keep getting a string error of "No sensors defined".
someone knows how to solve the issue?
Already tried creating a blank sensor and adding an http header of skip_sensor true.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-16-2025 08:34 PM
Here are a few steps you can try to resolve the "No sensors defined" error:
Check Sensor Configuration: Ensure your sensor is properly set up.
Clear Version Fields: Clear the version fields in the sensor record, potentially by modifying the XML directly.
Set Skip Sensor Parameter: Add skip_sensor=true in the REST Parameters.
Match Probe and Sensor Versions: Ensure versions are compatible.
Review Documentation: Look for any specific steps in the ServiceNow documentation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited Wednesday
Yeah, I ran into the same "No sensors defined" error—it’s like debugging fnf mods when one missing file breaks everything. Clearing the version fields (even editing the XML directly) actually helped, and adding skip_sensor=true in the REST params got it to finally move forward. Also, double-check your probe/sensor versions match—ServiceNow can be weirdly picky.
