> 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-runtime-security/cases-and-issues/customize-cases-and-issues/create-issue-exceptions/create-issue-exception-rules.md).

# Create issue exception rules

You create an issue exception by creating an exception rule. The following steps describe how to create an exception rule on the All Exceptions Rules page.

{% hint style="info" %}
You can create a maximum of 10 issue exceptions per day.
{% endhint %}

1. Navigate to Settings → Exceptions Configuration and click on the Exception Rules tab to display the All Exception Rules page.
2. Click + Add Exception, select Create new exception, and then click Next.
3. Complete the following fields, and then click Next:
   1. Rule Name
   2. Approver: Select an approver from the dropdown list.
   3. Exception End Date: The exception will expire on this date and the SLA timer will start to count down.
   4. Justification: Describe the business justification for creating this rule.
   5. Reason Category: Select a reason category from the dropdown list.
   6. External Exception ID: (Optional) Enter a ticket number or other tracking record.
4. Click Add filters, and then use the dropdown lists to create a filter that identifies the issues you want the exception rule to apply to.

   The query must return fewer than 100,000 issues.

   Click Next.
5. Review the summary of the proposed rule. If it is correct, click Create.

   The proposed exception rule will now appear in the All Exception Rules list with the status Pending Decision, and, if the Exception Rule Approval workflow is enabled, an Exception Rule Request email will be sent to the approver. The exception rule will not take effect until the request has been approved.


---

# 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-runtime-security/cases-and-issues/customize-cases-and-issues/create-issue-exceptions/create-issue-exception-rules.md?ask=<question>&goal=<endgoal>
```

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