> 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-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/forensics/forensic-investigations/manage-an-investigation/close-an-investigation.md).

# Close an investigation

Close an investigation and manage its 24-hour grace period.

Close an investigation when it is resolved or no longer needed.

{% hint style="info" %}
Closing starts a 24-hour grace period. Collections are deleted after that period. You can cancel the close request before deletion.
{% endhint %}

1. In the **Forensic Investigations** table, right-click the investigation.
2. Select **Close**.
3. In **Close Investigation**, review the investigation's exported evidence collections.

The investigation status changes to **Close Pending**. The timestamp shows when the investigation expires and data is deleted.

While closure is pending, right-click the investigation to select one of these actions:

* **Edit** — Update the name, description, or user permissions.
* **Open** — Cancel the close request.
* **Permanently delete** — Delete the investigation and associated data immediately. This action cannot be canceled.

***


---

# 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-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/forensics/forensic-investigations/manage-an-investigation/close-an-investigation.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.