---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Discovery status

# Discovery status {#ariaid-title1}

* Release version: Yokohama
* 
* Updated August 11, 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 a Discovery run from a schedule.
It enables you to monitor the progress, review detailed activity, and cancel an ongoing Discovery directly from the status form.
This functionality is essential for tracking Discovery executions, troubleshooting issues, and ensuring accurate configuration item (CI) data collection in your CMDB.
Show full answer Show less  

## Key Features

* **Accessing Discovery Status:** Navigate to Discovery \> Status to view records representing each Discovery execution, including date, mode, probe messages sent, and sensor processing counts.
* **Discovery Status Monitor Job:** Automatically analyzes Discovery schedules without status updates after a defined period, focusing on CIs, helping maintain up-to-date discovery health.
* **Detailed Monitoring Tools:**
  * **Refresh:** Updates related tabs such as Discovery Log and ECC Queue for ongoing Discoveries.
  * **Discovery Timeline:** Graphically displays probe and sensor activities over the course of the Discovery.
  * **Discovery Log Entries:** Records classification failures, CMDB updates, authentication failures, and other key actions.
  * **ECC Queue Entries:** Shows the flow of probe and sensor communications with actual XML payloads exchanged.
  * **Device History:** Summarizes all devices scanned and records sensor actions on the CMDB.
* **Discovery Status Record Fields:** Includes auto-generated record number, description of Discovery initiation (Scheduled or Discover Now), schedule name, Discovery state (e.g., Starting, Active, Completed, Canceled), probe progress, source type (Schedule, Quick Discovery, or API), Discovery type (CIs, IP addresses, Networks, Processes/Connections), max run time, and log state changes.
* **Cancel Discovery:** You can manually cancel a Discovery while it is in progress directly from its status record.
* **Device Classification Insight:** See which classification probe discovered a particular device via the classification probe column in the device list.
* **Data Retention:** By default, Discovery records are retained and displayed for 30 days.

## Practical Benefits for ServiceNow Customers

* Gain clear visibility into Discovery executions to monitor success and identify failures quickly.
* Utilize detailed logs and timelines to troubleshoot probe or sensor issues, enhancing Discovery reliability.
* Manage Discoveries efficiently by canceling problematic runs and reviewing device discovery histories.
* Access communication details via the ECC queue to understand integration points and data flow.
* Maintain up-to-date CMDB data by tracking the Discovery process and any state changes logged during runs.  
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, 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://servicenow-prod.fluidtopics.net/ik5zTaHnyf~vSY4NwewALw)**   
  You can manually cancel a discovery while it is in progress from the Discovery Status record.
* **[Discovery timelines](https://servicenow-prod.fluidtopics.net/8nPk~ZcRuy_3hACDQgEzIQ#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://servicenow-prod.fluidtopics.net/bpcRyGIfqThsVq23q3BEJg)**   
  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://servicenow-prod.fluidtopics.net/8pCbAkg_EhBt_rJJmHpqfA)**   
  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://servicenow-prod.fluidtopics.net/CIQEq9XeYjrEAd3sKWHEVg "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