> For the complete documentation index, see [llms.txt](https://docs.expel.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.expel.io/workbench-reference/investigations-and-incidents/reopen-an-investigation.md).
# Reopen an Investigation
{% hint style="info" %}
For more information about Investigations, see [Understanding Investigations](/workbench-reference/investigations-and-incidents/understanding-investigations.md).
{% endhint %}
You can reopen an Investigation at any time, such as if you do not agree with the decision or simply want more information. You should be sure to leave a comment with information about why you performed this action.
1. Select the Investigation on the **Activity > Investigations** page.
2. Select **Update Investigation** near the top of the screen.
3. Choose **Reopen**.
4. Select **Save**.
5. Select **Add comment** to add a comment or other notes about why you reopened the Investigation.
6. If you wish, select **Update Investigation** at the top of the page. You can then one of the following:
Assign the investigation back to the SOC analysts.
For example, you performed the remediation actions recommended, and want further information from the SOC.
Upgrade the investigation to an Incident.
For example, you review the activity and decide it might be a threat in your environment. The dialog box changes and prompts you for more information about what is going on.
* If you think this is a critical incident (a security breach may be happening right now), you should provide as much information as you can to help the SOC analysts or your team. The more information you can provide, the better the response is from the SOC analysts or from your team.
* Make sure you assign the incident to Expel if you want the SOC analysts to help. You can still work the incident on your side in the interim.
---
# 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://docs.expel.io/workbench-reference/investigations-and-incidents/reopen-an-investigation.md?ask=&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.
