Discovery status

  • Release version: Zurich
  • Updated June 16, 2026
  • 2 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Discovery status

    The Discovery status in ServiceNow provides a detailed summary of each Discovery execution launched from a schedule. It enables users to monitor the progress, troubleshoot issues, and manage Discovery runs directly from the status form. Users can also cancel an ongoing Discovery from this interface.

    Show full answer Show less

    Discovery schedules that show no status updates for a specified time are automatically analyzed by the Discovery Status Monitor job, which primarily applies to schedules discovering configuration items.

    Key Features

    • Accessing Discovery Status: Navigate to Discovery > Status to view individual Discovery executions, which show key details like execution date, mode, number of probes sent, and sensors processed.
    • Troubleshooting Tools: The status form includes controls to trace probe and sensor threads, allowing detailed troubleshooting of Discovery failures and the ability to rerun specific probes or sensors.
    • Discovery Timeline: A graphical representation of the Discovery run, showing each probe and sensor involved.
    • Discovery Log Entries: Logs provide detailed information about classification failures, CMDB updates, and authentication issues, with a record for every action linked to the Discovery.
    • ECC Queue Entries: Displays the communication flow between ServiceNow and external systems like MID Servers, including the actual XML payloads exchanged during Discovery.
    • Device History: Summarizes all devices scanned during the Discovery and the actions taken on the CMDB by sensors.
    • State and Run Details: Fields such as state, source, schedule, discovery type, maximum run time, and state change logging provide comprehensive context about each Discovery execution.
    • Cancel Discovery: Users can manually cancel a Discovery in progress directly from its status record.

    Practical Use for ServiceNow Customers

    ServiceNow customers can utilize the Discovery status to efficiently monitor Discovery jobs, quickly identify and resolve issues during discovery, and improve the accuracy and completeness of their CMDB. The detailed logs and timeline views support deep diagnostics, while features like canceling ongoing Discoveries provide operational control.

    By leveraging these capabilities, customers can ensure their Discovery processes run smoothly and maintain reliable configuration data essential for IT service management.

    The Discovery status provides a summary of a Discovery launched from a schedule. You can also cancel a Discovery that is in progress from the status form.

    Note:
    Discovery schedules that have no status updates for a over a defined number of minutes are analyzed automatically by the Discovery Status Monitor job. By default, this job applies to Discovery schedules that discover configuration items. For more information, see the Discovery Status Monitoring Job article in the Now Support Knowledge Base.

    To access the Discovery Status form, navigate to Discovery > Status and open the status record for a Discovery.

    Each record in the Status list represents the execution of a Discovery by a schedule and displays such high-level information as the date of the Discovery, the mode, the number of probe messages sent to devices, and the number of sensor records that were processed. A status record contains data that can help you troubleshoot a failed discovery. Use this data to troubleshoot the behavior of individual probes and sensors or even run those elements separately. Use the status controls to enter probe/sensor threads at any point for a specific Discovery, and then follow the process in either direction. You can also clearly see which classification probe ran and discovered a particular device by viewing the classification probe column in the device list.

    • Refresh: Refreshes the related tabs, including the Discovery Log and ECC Queue for discoveries still in progress.
    • Discovery timeline: The Discovery timeline is a graphical display of a discovery, including information about each probe and sensor that was used.
    • Discovery log entries: The Discovery Log shows information such as classification failures, CMDB updates, and authentication failures. A Discovery Log record is created for each action associated with a discovery status.
    • ECC queue entries: Entries in the ECC queue provide you with a connected flow of probe and sensor activity, as well as the actual XML payload that is sent to or from an instance.
    • Device history: The device history provides a summary of all the devices scanned during discovery, and what action sensors took on the CMDB.
    Note:
    By default, only 30 days of Discovery records are displayed in the status list at a time.
    The following Discovery status record shows the discovery of a load balancer using a pattern.
    Figure 1. Example Discovery status record
    Example Discovery status record
    Field Description
    Number An auto-generated number for the record.
    Description How this discovery was run. Typically, the description is Scheduled, but if you ran discovery manually from a Schedule, the record would show Discover Now in the Description field.
    Schedule The name of the Discovery schedule.
    State The state of the discovery:
    • Starting
    • Active
    • Completed
    • Canceled
    Started and Completed The number of probes started and completed during discovery.
    Source Optional read-only field that shows the source of the discovery, such as Schedule Discovery, or Quick Discovery. If the source of the Discovery was from an API call, the source is DiscoveryAPI.
    From Schedule (Read-only schedule data)
    Discover Shows the Discovery type. The possible types are: Configuration items, IP addresses, Networks, or Processes/Connections (ADM).
    Max Run Time Displays the maximum amount of time Discovery was permitted to run on this schedule.
    Log state changes Indicates that state changes were logged during this Discovery. These states can be seen in the Last and Current fields in theDiscovery Devices list in this form.