---
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


---

# Diagnostics

# Discovery Admin Workspace Diagnostics {#ariaid-title1}

Release version: Australia  
Updated November 5, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Admin Workspace Diagnostics

The Discovery Admin Workspace Diagnostics page enables ServiceNow customers to effectively prioritize and resolve errors and anomalies in IP-based and Cloud Discovery schedules.
Accessible via Workspaces \> Discovery Admin Workspace \> Diagnostics, this feature is available starting from Discovery Admin Workspace version 1.17.0.
The workspace helps streamline troubleshooting by grouping errors and anomalies, providing refined codes for actionable insights, and integrating AI-powered recommendations.
Show full answer Show less  

## Errors Tab

* **Error Management:** Displays all Discovery errors grouped by refined code, which uniquely identifies error types and suggests remediation steps.
* **Filtering and Sorting:** Errors can be prioritized using filters such as Severity, Category, and Domain, and sorted by Refined Code, Category, Severity, or Occurrence count.
* **Error Details:** Selecting an error opens a detailed page with root cause analysis, remediation guidance, and actionable options.
* **AI Insights:** Powered by ServiceNow Otto for Error Framework, this panel highlights the highest-impact and highest-leverage errors, providing summaries of affected schedules and recommended remediations. Note that this requires the ServiceNow Otto for Platform plugin (available from Australia Patch 3).

## Anomaly Detection Tab

* **Purpose:** Displays Discovery schedules with detected anomalies within a configurable time frame, helping administrators identify and address schedule issues.
* **Types of Anomalies:** Includes critical anomalies (failed runs), major anomalies (low CI discovery rate), and minor anomalies (long run time or high error count).
* **Data Visualizations:** Provides key indicators such as number of schedules with anomalies, failed schedules, low CI discovery rates, increased error counts, and long run times, all of which can be clicked to filter detailed schedule information.
* **Configuration and Actions:** Administrators can adjust thresholds for CI discovery rate, error count, and run time on the Settings page. The Actions menu offers quick access to anomaly settings and options to clear anomaly records.
* **Filtering:** Allows prioritization by schedule name, severity level (Critical, Major, Minor), and anomaly type (Failed schedule, Low CI discovery rate, Increased error count, Long run time).
* **Requirements:** Anomaly detection must be enabled and requires a minimum of five Configuration Items (CIs) per schedule from version 1.11.0 onwards.  
The Diagnostics page helps you prioritize and address errors and anomalies in IP-based and Cloud Discovery schedules.  
To access the Discovery Admin Workspace Diagnostics page, navigate to WorkspacesDiscovery Admin WorkspaceDiagnostics.  
Note:  
* The capabilities described here are available starting with Discovery Admin Workspace v1.17.0. Specific version requirements are noted for individual features where applicable.
* If the sn_disco_workspace.enable_error_framework system property is turned off, the Diagnostics page displays the legacy experience.
{#discovery-admin-workspace-diagnostics__ul_t11_fqt_ykc}

## Errors {#discovery-admin-workspace-diagnostics__section_ihx_3x3_2jc}

The Errors tab displays all Discovery errors grouped by refined code. Each error in the list shows the refined code, occurrence count, category, and domain. Use this tab to identify high-impact errors and trigger resolution
actions.

Use the Filter by options to prioritize the error list by Severity and Category. Selecting the Domain drop-down enables you to filter errors based on a specific domain.

You can filter the list of errors using the Search (![]()) icon. Use the Sort by drop-down menu to organize the results by Refined Code, Category, Severity, and Occurrences in either ascending or descending order.

Refined Codes
:   A refined code is a unique code assigned to every actionable error generated by Discovery. The refined code identifies the error type and recommends the appropriate remediation. Refined codes use the SN-DISC format.

    Select an error or its Occurrences
    link to open the Error Details page. The page displays the root cause, remediation steps, and available actions for that refined code. For more information, see [Discovery Admin Workspace Error Details](https://www.servicenow.com/docs/t3KQAV27M6znYFwQP6qLHg "The Error Details page displays the root cause and remediation steps for a specific Discovery error, along with the list of individual error instances associated with that error.").

    If Discovery doesn't start or a device isn't classified, see [Discovery start and classification issue resolution](https://www.servicenow.com/docs/~7Z1jj5MNxWtuH~ycrj_zQ "Use the Discovery Admin Workspace Diagnostics page to identify and resolve the cause when Discovery fails to start or classify a device.") for the refined codes that most commonly apply.

AI Insights
:   The Errors tab includes an AI Insights panel powered by ServiceNow Otto for Error Framework. The panel analyzes your current Discovery errors and surfaces the following:

    * Highest-impact errors: Errors that are affecting the most devices or schedules.
    * Highest-leverage errors: Errors where resolving a single instance clears the largest number of occurrences.

    {#discovery-admin-workspace-diagnostics__ul_gqs_my3_2jc}  
    Each insight includes a summary of affected schedules and devices, and recommended remediation steps. Select an error code link in the panel to navigate directly to that error.  
    Note:  
    ServiceNow Otto for Error Framework (com.sn_ef_gen_ai) is available starting with Australia Patch 3 and requires the ServiceNow Otto for Platform (sn_genai_platform) plugin. If the plugin is not enabled, the panel displays a prompt to enable it.

For more information about how the Error Framework works, see [Error Framework in Discovery Admin Workspace](https://www.servicenow.com/docs/NcS2hmKcIEcf83C060fNmw "Discovery Admin Workspace uses the Error Framework to surface actionable Discovery errors. You can review errors, understand their causes, and take steps to resolve them directly from the Diagnostics page.").

## Anomaly detection {#discovery-admin-workspace-diagnostics__section_xv5_lx3_2jc}

The Anomaly detection tab displays all of the Discovery schedules with anomalies detected in a certain time period. You can configure this time scale on the [Settings](https://www.servicenow.com/docs/oIyIPo_MBQKGNGgB0fzRbw "The Settings page enables you to customize and manage high-level Discovery properties so they’re tailored to meet your specific needs.") page.  
Important:  
This tab only displays anomalies when anomaly detection is enabled. Starting with v1.11.0, anomaly detection requires a minimum of five CIs to trigger. For more information, see the [Skip Anomaly Detection for small schedules](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2601541) article in the Now Support Knowledge Base.

Select the More Options icon (![]()), then select Refresh to refresh the data for each visualization in this section.  
{#discovery-admin-workspace-diagnostics__table_t33_rx3_2jc__entry__3}

| Report title | Type | Description |
|-|-|-|
| Schedules with anomalies | Indicator | Number of Discovery schedules with anomalies detected over a certain time period. Schedules are categorized as the following: * Critical anomalies: Failed to run. * Major anomalies: Have a low CI discovery rate. * Minor anomalies: Have a long run time or a high error count. {#discovery-admin-workspace-diagnostics__ul_u33_rx3_2jc} |
| Failed schedules | Indicator | Number of Discovery schedules that failed to run. |
| Low CI discovery rate | Indicator | Number of Discovery schedules that have a low CI discovery rate. Note: The threshold for the CI discovery rate can be configured on the Settings page. |
| Increased error count | Indicator | Number of Discovery schedules that have an increased error count. Note: The threshold for the error count can be configured on the Settings page. |
| Long run time | Indicator | Number of Discovery schedules that had a long run time. Note: The threshold for the run time can be configured on the Settings page. |
[Table 1. Data visualizations]

{#discovery-admin-workspace-diagnostics__table_t33_rx3_2jc}

Selecting any of the indicators filters the table to reflect the schedules represented in the data count. For each entry in the table, you can view details around the type and severity of anomalies.

The Actions drop-down menu provides a direct shortcut to the Settings page for configuring anomaly detection. Additionally, the menu includes a Clear all anomalies option so that
administrators can quickly remove records in the Discovery Schedule Anomaly \[discovery_schedule_anomaly\] and Discovery Schedule Anomaly Metrics \[discovery_schedule_anomaly_metrics\] tables.

Use the Filter by options to prioritize and address anomalies. Filter Discovery schedules by name using the Schedules drop-down menu. Additionally, you can prioritize the results with the Severity drop-down menu, which includes
options such as Critical, Major, and Minor. Use the Anomaly type drop-down menu to quickly view schedules with the same anomaly. Available options include Failed schedule, Low CI discovery rate,
Increased error count, and Long run time.

*[\>]: and then