> 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/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/customize-and-configure-cortex-xsoar/work-with-slas/search-incidents-using-sla-and-timer-fields.md).

# Search Incidents using SLA and Timer Fields

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 is still active, enter the following:
   * The name of the field
   * The run status
   * The due date. This is required for queries who 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, we are searching for all incidents that have an SLA timer called slatimer and fulfill the following criteria:

* The run status is neither ended nor paused AND the due date is later than now, meaning, the due date has not yet passed.

  OR
* Incidents whose run status is ended or paused and the SLA status is within the allotted time.

  `(-slatimer.runStatus:(ended paused) and slatimer.dueDate:>“now”) or (slatimer.slaStatus:“within”)`

In the following example, we are searching for all incidents that fulfill the following criteria:

* The run status is either ended or paused AND the due date is earlier than now, meaning, the due date has already passed.

  OR
* Incidents whose run status is ended or paused and the SLA status is late.

  `(-slatimer.runStatus:(ended paused) and slatimer.dueDate:<“now”) or (slatimer.slaStatus:“late”)`

In the following example, we are searching for all incidents that fulfill the following criteria:

* The run status is neither ended nor paused AND the due date is between now and 5 hours. The 5 hours represents our risk threshold.

  OR
* Incidents whose run status is ended or paused and the SLA status is Risk.

  `(-slatest.runStatus:(ended paused) and slatest.dueDate:>"now" and slatest.dueDate:<"in 300 minutes") or (slatest.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 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/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/customize-and-configure-cortex-xsoar/work-with-slas/search-incidents-using-sla-and-timer-fields.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.