> 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-commands-guide/triage-commands.md).

# Triage Commands

* [getTriagePresets](#gettriagepresets)
* [triageEndpoints](#triageendpoints)

#### getTriagePresets

***

Gets a list of available triage presets (collector configurations) for endpoint forensics. Use a preset's collector UUID with triageEndpoints to start a triage.

**Arguments**

There are no input arguments for this command.

<details>

<summary>Outputs</summary>

**Core.EndpointTriagePreset.uuid** *string*

The unique identifier of the triage preset.

**Core.EndpointTriagePreset.name** *string*

The name of the triage preset.

**Core.EndpointTriagePreset.os** *string*

The operating system the triage preset applies to.

**Core.EndpointTriagePreset.description** *string*

A description of the triage preset.

**Core.EndpointTriagePreset.created\_by** *string*

The user who created the triage preset.

**Core.EndpointTriagePreset.type** *string*

The type of the triage preset.

</details>

#### triageEndpoints

***

Initiates a forensics triage on the specified endpoints. Note the following requirements: up to 10 triage actions may run concurrently; all specified agents must have the Forensics License enabled; all specified agents must run the same OS (either Windows or macOS, not a mix); and the specified triage configuration must be of type Online (Online = True).

<details>

<summary>Arguments</summary>

| Argument Name   | Description                                                                                                                   | Required |
| --------------- | ----------------------------------------------------------------------------------------------------------------------------- | -------- |
| endpoint\_ids   | A comma-separated list of endpoint IDs to initiate triage on. Use the getEndpoints command to get the available endpoint IDs. | Required |
| collector\_uuid | The collector UUID (preset) to use for the triage. Use the getTriagePresets command to get the available collector UUIDs.     | Optional |

</details>

<details>

<summary>Outputs</summary>

**Core.EndpointTriage.TRIAGE\_ID** *string*

The unique identifier assigned to the created triage action.

**Core.EndpointTriage.SUCCESSFUL\_ENDPOINT\_IDS** *string*

A list of endpoint IDs where the triage action was successfully initiated.

**Core.EndpointTriage.UNSUCCESSFUL\_ENDPOINT\_IDS** *string*

A list of endpoint IDs where the triage action failed to initiate.

</details>


---

# 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-commands-guide/triage-commands.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.