> 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.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/work-with-slas/create-an-sla-trigger.md).
# Create an SLA Trigger
Create SLA triggers for Cortex XSOAR 6.14 playbook tasks.
Timers are specific tasks that you implement in playbooks to manage SLAs. The timers can be triggered to start, pause, or stop when a certain task occurs. For example, a timer can be triggered to stop for the **`Time to Assign`** field when the incident is assigned an owner, and to immediately start the timer for the **`Time to Remediation`** field.
Before you begin, if the playbook originates from a content pack, you need to either duplicate the playbook or detach it. If [detached](/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-development.md#UUID-014f89b7-473a-001a-58f4-b1c8cf0735ac_idf8f6e4e3-c3d0-4467-ac41-52ed72ab1f73), the playbook does not receive content pack updates.
1. Navigate to the **Playbooks** page.
2. Select the playbook to which you want to add the timer and click **Edit**.
3. Click the + symbol to add a new task or click an existing task to edit the task.
4. In the Timers tab, select the action that you want the timer to perform for the given task. Valid options are:
* **Start** - Starts the timer.
Note
Timers are not started automatically when an incident is created.
* **Pause** - Pauses the timer.
* **Stop** - Stops the timer. Once a timer is stopped, you can only reset a timer using the **resetTimer** command.
Note
Timers are automatically stopped when an incident is closed.
5. Select the field on which the timer is applied.
6. Click **Ok**.
---
# 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/xsoar-6-administrator-guide/6.14/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/work-with-slas/create-an-sla-trigger.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.