> 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-agentix/configure-cortex-agentix/cases-and-issues-configuration/create-issue-exceptions/create-an-exception-rule-from-an-issue.md).

# Create an exception rule from an issue

Create a Cortex AgentiX issue exception rule directly from an issue.

You can create an issue exception directly from an issue on the **Issues** page. This will result in an issue exception rule for a specific issue ID.

{% hint style="info" %}

### Note

You can create a maximum of 10 issue exception rules per day.
{% endhint %}

1. Navigate to Cases & Issues>Issues.
2. Right-click on the issue that you want to create an exception for, select Manage Issue>Except Issue.
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. Verify that the correct issue appears in the table, and 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 **Exception Rules** tab on the **Issue Exception & Exclusion** page 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-agentix/configure-cortex-agentix/cases-and-issues-configuration/create-issue-exceptions/create-an-exception-rule-from-an-issue.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.