> 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/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-lifecycle/receive-notification-on-an-incident-fetch-error.md).

# Receive Notification on an Incident Fetch Error

Configure Cortex XSOAR 6.15 notifications for incident fetch errors.

The administrator and Cortex XSOAR users on the recipient’s list receive a notification when an integration experiences an incident fetch error, which occurs for a state transition from **Success** to **Failure** during an incident fetch.

{% hint style="warning" %}
Because notifications are triggered only by the state transition, you will not receive an alert if:

* A new integration instance fails its first fetch attempt (since a successful fetch has not yet occurred).
* You force a fetch failure for testing purposes before a successful fetch has occurred.
  {% endhint %}

Cortex XSOAR users can select their notification method, such as email, from their user preferences. Administrators with multiple instances of mail sender can choose to receive one email notification instead of multiple email notifications.

{% hint style="info" %}
The connectivity behavior that exists between third-party applications may trigger a fetch failure, which will send a notification to an administrator and users. If the fetch operates correctly just after the notification was sent, the notification may no longer be relevant.
{% endhint %}

**Before you begin**

In the integration instance, ensure that you select the **Fetch Incidents** checkbox.

1. Select Settings → About → Troubleshooting → **Add Server Configuration**.
2. Add the following keys and values:

   | Key                                   | Value                                                         |
   | ------------------------------------- | ------------------------------------------------------------- |
   | `module.health.notification.users`    | List of names in CSV format, for example `user1,user2,user3`. |
   | `message.ignore.failedFetchIncidents` | `false`.                                                      |
3. (Optional) Administrators that have multiple instances of a mail sender configured that want to receive only one email notification should select the **Do not use by default** option in the integration instances that should not be used to send emails.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-lifecycle/receive-notification-on-an-incident-fetch-error.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 `build a script that syncs our docs to a CMS` 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.