> 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/manually-de-duplicate-incidents.md).

# Manually De-Duplicate Incidents

You can manually de-duplicate incidents from the **Incidents** page or the **Related Incidents** tab.

* To de-duplicate incidents from the **Incidents** page:
  1. Select the incident checkboxes that are duplicates.
  2. Click **Mark as Duplicate**.
  3. Type the ID of the incident that you want to retain.
  4. Click **Validate**.
  5. Click **Close others as duplicate**.

     The duplicated incident is removed from the table.
* To de-duplicate incidents from the **Related Incidents** tab:
  1. From the **Incidents** page, select the relevant incident checkbox.
  2. In the **Related Incidents** tab, click the related incident you want to de-duplicate.
  3. Click **Close as duplicate**.

     The duplicated incident is closed and marked as duplicate.


---

# 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/manually-de-duplicate-incidents.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.