---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Discovery status

# Discovery status {#ariaid-title1}

Release version: Australia  
Updated November 19, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 comprehensive summary of each Discovery execution initiated by a schedule.
It allows customers to monitor the progress, troubleshoot issues, and manage Discovery runs effectively.
You can also cancel an ongoing Discovery directly from the status form.
Show full answer Show less  
The Discovery Status Monitor job automatically analyzes Discovery schedules that have no status updates for a specified time, focusing primarily on schedules that discover configuration items. This helps maintain accurate and timely monitoring of Discovery processes.

## Access and Key Information

Access the Discovery Status form via **Discovery \> Status** to view individual Discovery execution records. Each record displays critical information including:

* Date and mode of Discovery
* Number of probe messages sent and sensor records processed
* Discovery schedule and type (e.g., Configuration items, IP addresses, Networks, Processes/Connections)
* State of the Discovery (Starting, Active, Completed, Canceled)
* Source of the Discovery (e.g., Schedule Discovery, Quick Discovery, DiscoveryAPI)
* Maximum permitted run time for the schedule
* Log state changes during Discovery for device status tracking

By default, only 30 days of Discovery records are shown to keep the status list manageable.

## Key Features

* **Refresh:** Updates related tabs such as Discovery Log and ECC Queue for ongoing Discoveries.
* **Discovery timeline:** Provides a graphical overview of the Discovery run, detailing each probe and sensor used.
* **Discovery log entries:** Records detailed information including classification failures, CMDB updates, and authentication failures to assist troubleshooting.
* **ECC queue entries:** Displays the flow of probe and sensor communications, including XML payloads exchanged between the instance and MID Server.
* **Device history:** Summarizes all devices scanned during the Discovery and the actions sensors took on the CMDB.
* **Cancel Discovery:** Enables manual cancellation of an active Discovery directly from the status record.

## Practical Benefits for ServiceNow Customers

This Discovery status functionality empowers customers to:

* Monitor Discovery executions for timely and successful completion.
* Identify and troubleshoot probe and sensor issues quickly using detailed logs and timelines.
* Understand device discovery results and CMDB updates via device history summaries.
* Manage Discovery schedules efficiently by canceling problematic or unnecessary runs.
* Maintain operational health of Discovery processes through automated status monitoring.  
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.{#c_DiscoveryStatus__shortdesc_discovery-status}  
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](https://support.servicenow.com/kb?id=kb_article_view&sys_kb_id=c2a6f4bf935a1ed0f538fb2d6cba10be) article in the Now Support Knowledge Base.

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

Each record in the Status list represents the execution of a Discovery by a schedule. It displays high-level information such as the date of the Discovery and the mode. It also shows the number of probe messages sent to devices and the number of sensor records 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.{#c_DiscoveryStatus__p_feature-intro}  
* 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, Configuration Management Database (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. They also include 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.
{#c_DiscoveryStatus__ul_rrh_znj_c1b}  
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  
{#c_DiscoveryStatus__table_nl1_yv5_lz__entry__2}

| 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 {#c_DiscoveryStatus__ul_nj5_mx5_lz} |
| 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. |
[ ]

{#c_DiscoveryStatus__table_nl1_yv5_lz}
* **[Cancel a Discovery from a Discovery Status](https://www.servicenow.com/docs/lrfF576Be2onqXB2Rt06AA)**   
  You can manually cancel a discovery while it is in progress from the Discovery Status record.
* **[Discovery timelines](https://www.servicenow.com/docs/5mGn4LoY1LpXEwxUYeD3_w#c_DiscoveryStatusTimelines)**   
  A Discovery timeline generates a graphical display of a Discovery Status record, including information about each probe and sensor that was used in the discovery.
* **[The ECC queue for Discovery](https://www.servicenow.com/docs/BVFgMoSEO4IOOWIXFgUsrA)**   
  The External Communication Channel (ECC) Queue is a connection point between your ServiceNow instance and other systems that integrate with it, most commonly a MID Server.
* **[Discovery device history](https://www.servicenow.com/docs/HBPw5akD4d7I20ynITlTyQ)**   
  The Devices Related list in the Discovery Status form provides a summary list of all the devices scanned.

**Related tasks**   

* [Schedule a horizontal discovery](https://www.servicenow.com/docs/VO0owNull6HAfXGFWMKxhg#t_CreateADiscoverySchedule "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.")

*[\>]: and then


