> 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.13/learn-about-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

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="info" %}

### Important

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" %}

### Note

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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-lifecycle/receive-notification-on-an-incident-fetch-error.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.