> 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/manage-sla-and-timer-fields-in-an-incident.md).

# Manage SLA and Timer Fields in an Incident

You can manage the timers and SLA for a specific incident. This enables you to manage SLAs on a global level within the SLA fields, and on a more granular level within specific incidents when the need arises. For example, if the severity of the incident dictates that you decrease the response time for the given incident.

1. SLA Fields

   You can use commands to set the SLA for a specific SLA field in a specific incident using the **setIncident** command and adding the SLA field for which to set the time.

   If you do not enter a value for the slaField parameter, the time you enter is applied to the incident's Due Date.

   **Example**

   The following example shows you how to change the Time to Detection field to 30 minutes for the current incident:

   `!setIncident sla=30 slaField=timetodetection`

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>When defining the values for the slaField and timer commands, all values must be in lowercase and cannot have any spaces.</p></div>
2. Timer Fields

   You can use commands to change the state of a timer for an incident using the following:

   * **startTimer** - Starts the timer. This command should also be used to restart a paused timer.

     <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Timers are not started automatically when an incident is created.</p></div>
   * **pauseTimer** - Pauses the timer.
   * **stopTimer** - Stops the timer. Once a timer is stopped, you can only reset a timer using the **resetTimer** command.

     <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><h3>Note</h3><p>Timers are automatically stopped when an incident is closed.</p></div>
   * **resetTimer** - Resets a timer. This command should be used to enable a timer that was stopped.

   **Example**

   The following example shows you how to pause a timer for a specific field in the current incident:

   `!pauseTimer timerField=timetodetection`

   You can specify the incidentID to change the timer for a different incident.


---

# 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/manage-sla-and-timer-fields-in-an-incident.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.
