> 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-xsoar-8-on-prem/8.10/configure-cortex-xsoar/slas/search-incidents-for-timerslas.md).

# Search incidents for Timer/SLAs

Search incidents by SLA and timer fields in Cortex XSOAR 8.10 On-prem.

You can search for incidents based on their SLA in several ways:

* Based on the SLA status.

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>The SLA status is not defined unless the timer is in a stopped mode, meaning either paused or ended.</p></div>
* Based on an SLA field.
* Based on a timer field.

For example, you can search for all of the timer fields that are currently running, or you can search for all incidents with a specific SLA status.

1. Navigate to the **Incidents** page.
2. To search for an incident whose Timer/SLA is still active, enter the following:
   * The name of the field
   * The run status
   * The due date

     This parameter is required for queries whose run status is neither ended nor paused, to improve query performance.
3. To search for an incident whose timer is no longer active, enter the SLA Status.

#### Examples

In the following example, search for all incidents using the Remediation SLA field that fulfill the following criteria:

* The Remediation SLA run status has not ended or paused AND the due date is later than now OR the SLA status is within time.

  `(-remediationsla.runStatus:(ended paused) and remdiationsla.dueDate:>now) or (remediationsla.slaStatus:"within")`
* The Remediation SLA run status has not ended or paused AND the due date is earlier than now OR the SLA status is late.

  `(-remediationsla.runStatus:(ended paused) and remediationsla.dueDate:<now) or (remediationsla.slaStatus:late)`
* The Remediation SLA run status has not ended or paused AND the due date is between now and five hours (the five hours represent our risk threshold) OR the SLA status is Risk.

  `(-remediationsla.runStatus:(ended paused) and remediationsla.dueDate:>now and remediationsla.dueDate:<"in 300 minutes") or (remediationsla.slaStatus:risk)`


---

# 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-xsoar-8-on-prem/8.10/configure-cortex-xsoar/slas/search-incidents-for-timerslas.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.