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


---

# Error framework

# Error Framework in Discovery Admin Workspace {#ariaid-title1}

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

The Error Framework in Discovery Admin Workspace centralizes actionable Discovery errors, allowing ServiceNow administrators to review, understand, and resolve issues efficiently from the Diagnostics page.
It enhances error visibility by grouping errors by category and severity and providing detailed context and remediation guidance directly within the workspace.
Show full answer Show less  

## Key Features

* **Centralized Error View:** Errors are organized by severity and category with contextual details including affected devices and Discovery schedules.
* **Solution-Focused Records:** Each error includes root cause analysis and remediation steps, plus actions such as retrying discovery or adding IPs to exclusion lists.
* **AI-Powered Insights:** The Diagnostics page features an AI Insights panel that prioritizes high-impact errors and suggests quick wins to optimize resolution efforts, powered by ServiceNow Otto.
* **Error Classification:** Errors are classified through base rules and refined post-discovery to update severity and relevance, filtering out informational errors to focus attention on actionable items.
* **Error Lifecycle Management:** Errors can be opened, closed, or ignored, with closed and ignored records retained for 7 days and detailed error instances retained for 90 days.
* **Domain Filtering:** Allows focusing on errors relevant to specific domains for targeted troubleshooting.
* **Configurable Enablement:** Enabled by default, with the option for administrators to disable the framework to revert to legacy diagnostics.

## Practical Use and Benefits

ServiceNow customers benefit from a streamlined, actionable error management system that reduces investigation time by providing enriched context and guided remediation. AI prioritization helps focus efforts on the most critical and impactful errors, improving Discovery reliability and reducing downtime. The ability to trigger resolution actions directly from error records enhances operational efficiency.

## Requirements and Roles

* The ServiceNow AI Platform must be on Brazil release or Australia release starting with Patch 3.
* Discovery Admin Workspace version 1.17.0 or later must be installed.
* Access requires the **discoveryadmin** role.
* ServiceNow Otto plugins are needed to fully utilize AI insights and agents for error analysis and remediation.  
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.

## Benefits {#error-framework-daw__section_ibb_rtx_x3c}

The Error Framework in Discovery Admin Workspace provides the following benefits:

* A centralized view of Discovery errors grouped by category and severity.
* Contextual details for each error, including affected devices and Discovery schedule.
* Solution-focused error records that guide you to the root cause and remediation steps first.
* Actions you can trigger directly from an error record to help resolve the issue.
* AI-powered insights that prioritize your errors and surface high-impact items and quick wins.
* Aggregated error statistics to identify patterns across discovery runs.
* A domain filter to focus on errors relevant to your domain.

## How it works {#error-framework-daw__section_qdl_rtx_x3c}

When Discovery runs, it logs actionable errors to the Error Framework. Each error includes a unique error code, context about where and why it occurred, and one or more resolution actions. The Diagnostics page
in Discovery Admin Workspace displays these errors on the Errors tab.

After Discovery completes, the framework refines error classifications using enrichment data from the discovery run. For example, if a device initially logged an SNMP connection error but was successfully
discovered through another protocol, reﬁnement updates the error to an informational state. Errors downgraded to informational severity are filtered from the default view so you can focus on errors that need attention.

Error Framework is enabled by default. Administrators can disable it by setting the sn_disco_workspace.enable_error_framework system property to <kbd class="ph userinput">false</kbd>. When Error Framework is
inactive, Discovery reverts to the legacy Diagnostics experience.  
Note:  
The Error Framework only logs actionable errors that have documented resolution steps. It doesn't replace system-level debug logging.

Error Classification
:
    The framework classifies Discovery errors using two levels of rules:

    * Base rules: ServiceNow-provided rules that map known Discovery log patterns to standardized error codes in the SN-DISC format.
    * Refinement rules: Rules that further classify errors based on additional context gathered after the discovery run completes. Refinement can change an error's code or downgrade its severity. Default refinement rules are provided for known Discovery scenarios.
    {#error-framework-daw__ul_ycc_ghv_fjc}

    The framework processes errors through base classification first, then applies refinement. As part of this process, each error record is enriched with data from related Discovery sources, including CMDB records,
    credential affinities, IP address details, and Discovery schedule configuration. This context is available on the error record and reduces the need to navigate between multiple tables during investigation. The refined error code is what
    appears on the Errors tab of the [Diagnostics](https://www.servicenow.com/docs/lDVudWreRZ8s3rW8uKl3Bw "The Diagnostics page helps you prioritize and address errors and anomalies in IP-based and Cloud Discovery schedules.") page. Errors downgraded to informational severity are filtered from the default view, so you can focus on errors that need attention.

Error severity levels
:   Each error is assigned a severity level based on its impact on discovery. The following table describes the severity levels.{#error-framework-daw__table_yyn_3hv_fjc__entry__2}

    | Severity | Description |
    |-|-|
    | Critical | The error prevents discovery from completing for the affected device or schedule. |
    | High | The error significantly affects discovery results but doesn't stop the run. |
    | Medium | The error may affect some discovery results. Review and resolve when possible. |
    | Low | The error has minimal impact. Address when convenient. |
    | Info | Informational only. No action is required. |
    [ ]

    {#error-framework-daw__table_yyn_3hv_fjc}

Error states
:
    Errors move through the following states during their life cycle:

    * Open: The error is active and hasn't been resolved.
    * Closed: The error has been resolved.
    * Ignored: The error has been acknowledged and suppressed from active views.

    {#error-framework-daw__ul_tw4_khv_fjc}  
    Note:  
    Closed and ignored error records are retained for seven days. Error instance records are retained for 90 days.

Error actions
:
    Each error code can have one or more actions associated with it. Actions are available from the error record and can include the following types:

    * Changing the state of an error instance to Open, Ignored, or Resolved.
    * Adding the affected IP address to the global exclusion list.
    * Retrying discovery for the affected device or schedule.
    * Displaying a message with remediation steps to resolve the error.
    {#error-framework-daw__ul_orh_mhv_fjc}

    Note:  
    Available actions vary by error type.

    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.").

AI insights

:   The [Diagnostics](https://www.servicenow.com/docs/lDVudWreRZ8s3rW8uKl3Bw "The Diagnostics page helps you prioritize and address errors and anomalies in IP-based and Cloud Discovery schedules.") page includes an AI Insights panel powered by ServiceNow Otto for Error Framework. The panel analyzes your current Discovery errors and generates a prioritized summary to help you focus on the most important issues first. Insights are scoped to the domain selected in the Domain
    drop-down and update automatically when you change filters on the Errors tab.

    The panel surfaces the following:

    * Highest-impact errors that are affecting the most devices or schedules.
    * Quick wins, which are errors that can be resolved with minimal effort.
    {#error-framework-daw__ul_gwb_4hv_fjc}  
    You can also use ServiceNow Otto agents to analyze a specific error code and receive a summary with remediation steps on demand.  
    Note:  
    * ServiceNow Otto for Error Framework (com.sn_ef_gen_ai) is available in 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.
    * The Error Analysis and Remediation Workflow and Error Analysis and Remediation Agent are enabled by default with the ServiceNow Otto for Error Framework plugin.
    * To interact with an agent, you must first [Activate the ServiceNow Otto panel standard chat](https://www.servicenow.com/docs/access?context=activate-now-assist-panel&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US).
    {#error-framework-daw__ul_ejd_qt1_gjc}

## Roles {#error-framework-daw__section_d4q_bwx_x3c}

The discovery_admin role is required to access Discovery Admin Workspace and interact with errors.

## Requirements {#error-framework-daw__section_s2v_2wx_x3c}

The following are required to use Error Framework features in Discovery Admin Workspace:

* The ServiceNow AI Platform must be running the Brazil release, or the Australia release starting with Patch 3.
* Discovery Admin Workspace must be installed, starting with v1.17.0.
{#error-framework-daw__ul_blz_fwx_x3c}

