> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cases-and-issues/customize-cases-and-issues/create-issue-exceptions/view-issue-exception-rules.md).
# View issue Exception Rules
View important details about issue exception rules, such as the status of a rule and how many issues are impacted by a rule, on the All Exception Rules page.
To view the All Exception Rules page, navigate to Settings โ Exceptions Configuration โ Exception Rules.
## **All Exception Rules field descriptions**
The table below describes each field in the All Exception Rules table.
| Field | Description |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Approver Email | Email address of the approver. |
| Approver Name | Name of the approver. |
| Backward Scan Status | Processing status of the exception rule. It indicates whether or not the exception has taken effect.
Possible values include:
- Pending: the system has not started excepting issues.
- In progress: the system is actively updating the issues.
- Failed: issue exception failed
- Done: all affected issues have been marked as excepted
|
| Decision Justification | Justification provided by the approver for approving or rejection the exception rule request. |
| Exception ID | Unique ID for the exception rule. |
| Expiration Date | Date the exception expires. This is the Exception End Date that was specified when the exception rule was created. |
| External Exception ID | Optional reference provided when the rule was created. |
| Impacted Issues | ?Number of issues impacted by the exception request. |
| Justification | Description of the business justification for this exception. |
| Justification Category | High-level category of the business justification. |
| Name | Name of the rule. |
| Requestor Email | Email address of the person who created the exception rule. |
| Requestor Name | Name of the person who created the exception rule. |
| Rule | The issue ID or other issue identifiers used to define which issues the exception applies to. |
| Status | The current workflow status for the rule. Refer to the Exception Rule status descriptions table for a description of each status. |
## **Exception rule status descriptions**
The following table describes the status field values for exception rules.
| Status | Description |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Approved | The rule has been approved and is active. |
| Disabled | The rule has been manually disabled. |
| Expired | The Exception End Date for the rule has passed. |
| No Decision Made | The approver did not respond to the issue exception rule request within seven days, so the request timed out. |
| Pending Decision | The issue exception rule request was sent to the approver. The approver has not yet responded but the request is still within the seven-day response window. |
| Rejected | The approver rejected the issue exception rule request. |
| Self Approved | The rule was created when the Exceptions Require Approval setting was toggled โoffโ. |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-posture-management/cases-and-issues/customize-cases-and-issues/create-issue-exceptions/view-issue-exception-rules.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.