---
sourceDocument: Zurich Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/governance-risk-compliance

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# View and update exceptions

# Viewing and updating Governance, Risk, and Compliance exceptions {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Report exceptions as it is critical for businesses to quickly identify and address
key business process issues before they become a problem. Using exceptions to manage errors
has advantages over traditional error-management techniques.

## Before you begin

Role required: sn_grc.admin

## About this task

An exception report is a document that lists instances in which actual performance is
deviated from expectations. GRC exception is a capability using
which you can record or associate business exceptions with GRC
objects such as citations, automated factors, and so on. Each exception record has
details such as the category of the exception, the record in the table, and the
field with which the exception is associated. The administrator can view the list of
exceptions and resolve them. Whenever an exception is raised, the solution to
resolve the exception is also given in the exception description. The administrator
uses the proposed solution to resolve the exception. An example of an exception is
when a user has not configured a risk assessment methodology but is trying to
perform an object assessment. When an administrator resolves one type of exception,
all other similar exceptions get resolved.

## Procedure

1. Navigate to GRC ExceptionsException Report.
2. Open the exception record you want to resolve.
3. On the form, fill in the field.  
   {#viewing-and-updating-grc-exceptions__table_p33_rrc_qmb__entry__2}

   | Field | Description |
   |-|-|
   | Number | Unique number of the exception that is raised. |
   | Exception category | Category to which an exception belongs. The choices are: * Configuration: Example: A risk administrator tries configuring a form and giving a user the authority to perform a task for which the user does not have the right role. * Runtime: Example: When something runs automatically such as an Indicator. {#viewing-and-updating-grc-exceptions__ul_mpk_15c_qmb} |
   | State | State of exception. The default state is Open. |
   | Application | Application to which the exception belongs. |
   | Description | Detailed description of the exception and the possible solution for resolution. |
   | Exception Record Details ||
   | Source table | Table on which the exception has occurred. |
   | Record reference | Record on which the exception has occurred. For example, an exception is raised on a risk assessment instance response. |
   | Column reference | The column that contains the record. |
   | Activity ||
   | Additional comments | Notes on the resolution of the exception or any other additional information. |
   | Activities | Displays the stream of activities on the exception. |
   [Table 1. Exception form]

   {#viewing-and-updating-grc-exceptions__table_p33_rrc_qmb}
4. Click Update after you change the state of the exception.
5. Click Delete to delete the record.

*[\>]: and then