> 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-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/forensics/data-collection/hunting/hunt-status.md). # Hunt status Monitor Cortex XSIAM hunt searches and results across targeted endpoints. 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 **Investigation & Response** → **Forensics**. From the investigations 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 in Cortex XSIAM.
FieldDescription
Endpoint nameAgent hostname.
Endpoint IDAgent unique ID.
Action IDA unique identifier for the agent action.
NameName of search.
Status

Shows one of the following statuses of the search:

  • Pending
  • In progress
  • Completed successfully
  • Failed
  • Timeout
Artifact category

Name of category for the search.

Example: Process execution

Artifact

Artifact targeted by this search.

Example: Amcache

ResultsNumber of results received for the search.
Last updatedLatest time results were received for this action.
Parameters

The string that describes the search parameters.

Example: C:\Users* File Name Regex: *.exe

Creation timeTimestamp 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 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-xsiam/detect-investigate-and-respond-to-threats/investigation-and-response/forensics/data-collection/hunting/hunt-status.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.