Find the cause of a "Probe not found" error

task australia Updated Sep 10, 2026 1 min read t_FindTheCauseOfAProbeNotFoundError.md
Raw file servicenow.com

Verify the correct sys_id of the probe associated with the probe parameter in the payload of the ECC Queue input record.

Before you begin

Role required: discovery_admin or admin

Procedure

  1. Record the sys_id of the probe as it appears in the ECC Queue payload.

    [Omitted image "DiscoveryProbeNotFoundError.png"] Alt text: ECC Queue payload sample

  2. Navigate to Discovery Definition > Probes and open the record for the probe you want to inspect.

  3. Right-click in the record's header bar.

  4. Select Copy sys_id from the context menu.

    Follow browser instructions to copy the sys_id if browser security measures restrict this function.

  5. Compare this value with the sys_id of the probe from the payload.

    If the sys_id of the probe record does not match the value in the payload, try to determine the cause of the incorrect value.

Parent Topic:Discovery error messages

Related topics

Find the cause of a sensor error message

Find the cause of a "No Sensor Defined" error message

Fix the cause of a sensor error message

Search documentation
Search document titles and file paths on the australia branch