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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Discovery status

# Discovery status {#ariaid-title1}

Release version: Brazil  
Updated October 8, 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 feature in ServiceNow provides a detailed summary and real-time monitoring of Discoveries launched from schedules.
It enables you to track the progress, results, and any issues during discovery runs.
You can also cancel ongoing Discoveries directly from the status form.
Show full answer Show less  
Discovery schedules without recent status updates are automatically monitored by the Discovery Status Monitor job, which helps identify stalled or failed Discoveries, especially those involving configuration items.

## Accessing and Using Discovery Status

Access the Discovery Status form by navigating to **Discovery \> Status**, where each record corresponds to one Discovery execution. Key information includes the Discovery date, mode, number of probes and sensors processed, and the schedule used.

This status data is essential for troubleshooting failed Discoveries by allowing you to analyze individual probes and sensors, run them separately, and track their behavior step-by-step.

## Key Features

* **Refresh:** Updates related tabs such as the Discovery Log and ECC Queue for ongoing Discoveries.
* **Discovery timeline:** Graphically displays the sequence and details of probes and sensors used during the Discovery.
* **Discovery log entries:** Records actions like classification failures, CMDB updates, and authentication issues for detailed troubleshooting.
* **ECC queue entries:** Shows the flow of probe and sensor activity along with the XML payloads exchanged, providing deep insight into Discovery communication.
* **Device history:** Summarizes all devices scanned during the Discovery and the actions sensors performed on the CMDB.

## Discovery Status Record Details

Each Discovery status record includes:

* **Number:** Auto-generated record identifier.
* **Description:** Indicates how the Discovery was run (e.g., Scheduled or Discover Now).
* **Schedule:** Name of the Discovery schedule.
* **State:** Current state of the Discovery (Starting, Active, Completed, Canceled).
* **Started and Completed:** Counts of probes initiated and finished.
* **Source:** Origin of the Discovery (e.g., Schedule Discovery, Quick Discovery, or API).
* **Discover Type:** Type of Discovery such as Configuration items, IP addresses, Networks, or Processes/Connections (ADM).
* **Max Run Time:** Maximum allowed runtime for the Discovery schedule.
* **Log state changes:** Indicates if state changes are logged, visible in the Discovery Devices list.

## Additional Capabilities

* You can manually cancel an ongoing Discovery from the Discovery Status record.
* The Discovery timeline provides a useful graphical overview of probe and sensor activity.
* The ECC Queue shows detailed communication between the ServiceNow instance and MID Servers during Discovery.
* The Device history list offers a comprehensive view of all scanned devices and CMDB updates.

## Practical Benefits for ServiceNow Customers

Using Discovery status helps you confidently monitor and manage Discovery operations, quickly identify and troubleshoot issues with probes and sensors, and maintain an accurate and up-to-date CMDB. The ability to cancel Discoveries and view detailed logs and timelines ensures efficient and controlled Discovery processes.  
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 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.{#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, 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.
{#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/uUqLUE64_bJoaznTavwYFg)**   
  You can manually cancel a discovery while it is in progress from the Discovery Status record.
* **[Discovery timelines](https://www.servicenow.com/docs/bF7I4MZJqxPBzaUMLMX3VA#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/rlkd7L6m_DNEkwS7ySYSLg)**   
  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/~81Lx~wKUoAewNHmcKx7mQ)**   
  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/A3BVdNwrtvD7FvMzmPuJVA#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