> 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.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-de-duplication.md).

# Incident De-Duplication

In the lifecycle of incident management, there are cases when incidents are duplicated. Cortex XSOAR provides the following de-duplication capabilities:

* **Manual De-Duplication**: You can manually de-duplicate incidents from the **Incidents** page or the **Related Incidents** page. To de-duplicate incidents manually, see [Manually De-Duplicate Incidents](/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-de-duplication/manually-de-duplicate-incidents.md).
* **Automatic De-Duplication**: You can automate de-duplicate incidents by using [Pre-Process Rules](/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/pre-process-rules.md) and [Scripts](/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-de-duplication/automatic-de-duplication-using-scripts.md).
* **Automations**: You can create an automation that creates child incidents from duplicates.
* **Playbooks**: Identify, review or close duplicate incidents using playbooks.

  There are several out-of-the-box playbooks you can run to identify and close duplicate incidents. Alternatively, you can use these playbooks as the basis for customized de-duplication playbooks. For example, instead of automatically closing the duplicate incidents, include a manual review of the duplicate incidents.

  | Playbook                                                                                | Description                                                                                                   |
  | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------- |
  | [Dedup - Generic v4](https://xsoar.pan.dev/docs/reference/playbooks/dedup---generic-v4) | Identifies duplicate incidents using the machine learning model (used mainly for phishing).                   |
  | [DeDup - Generic v3](https://xsoar.pan.dev/docs/reference/playbooks/dedup---generic-v3) | Identifies duplicate incidents using one of the supported methods, such as rules, text, and machine learning. |


---

# 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.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/incidents/incident-de-duplication.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.