> 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-3.x/cortex-xdr-3.x-documentation/detect-threats-and-analyze-data/forensic-investigations/data-collection/hunting/hunt-status.md).

# Hunt status

Hunts consist of searches across multiple endpoints and those searches can take time to return results from all of the targeted endpoints. To view the status of all of the searches contained within a hunt, go to **Incident Response** → **Investigation** → **Forensics**. From the investigation table, click the investigation link. From the **Collections** tab, select **Hunt** and from the **Status** column of the hunt, click **Actions**. This launches a new browser tab displaying the **Actions** table. Within the **Actions** table, you can scroll or use the filters to see the status of any search within a hunt across any of the targeted endpoints.

Using this information, you can identify the successful and failed searches and take the necessary action.

| Field             | Description                                                                                                                                                          |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Endpoint name     | Agent hostname.                                                                                                                                                      |
| Endpoint ID       | Agent unique ID.                                                                                                                                                     |
| Action ID         | A unique identifier for the agent action.                                                                                                                            |
| Name              | Name of search.                                                                                                                                                      |
| Status            | <p>Shows one of the following statuses of the search:</p><ul><li>Pending</li><li>In progress</li><li>Completed successfully</li><li>Failed</li><li>Timeout</li></ul> |
| Artifact category | <p>Name of category for the search. </p><p>Example: <code>Process execution</code></p>                                                                               |
| Artifact          | <p>Artifact targeted by this search.</p><p>Example: <code>Amcache</code></p>                                                                                         |
| Results           | Number of results received for the search.                                                                                                                           |
| Last updated      | Latest time results were received for this action.                                                                                                                   |
| Parameters        | <p>The string that describes the search parameters.</p><p>Example: <code>C:\Users\* File Name Regex: \*.exe</code></p>                                               |
| Creation time     | Timestamp when the search was created.                                                                                                                               |


---

# 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/cortex-xdr-3.x/cortex-xdr-3.x-documentation/detect-threats-and-analyze-data/forensic-investigations/data-collection/hunting/hunt-status.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.