> 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.7/configure-cortex-xsoar/slas/use-sla-and-timer-field-commands-manually-in-the-cli.md).

# Use SLA and Timer field commands manually in the CLI

You can manage the timers and SLA for a specific incident manually in the CLI, which enables you to manage SLAs on a global level and 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.

#### Set Timer/SLA fields

Use the `setIncident` command to set the SLA incident due to date or to set a specific SLA field in an incident. When adding the `sla` parameter to the command, it sets the time for the incident's due date. If you also add the `slaField` you set the SLA for the incident field.

For example, to change the **Time to Assignment** field to 30 minutes in the current incident:

`!setIncident sla=30 slaField=timetoassignment`

To change the SLA time to February 1, 2024, at 11.12 am:

`!setIncident sla=2024-02-01T11:12`

{% hint style="info" %}

### Note

When defining the values for the `slaField` use the machine name for the field, which is lowercase and without spaces. You can check the machine name by editing the incident field. For example, the Remediation SLA field is `remediationsla`.
{% endhint %}

#### Start/stop Timer/SLA fields

Use the following commands in the CLI:

| Command      | Description                                                                                                                                                                                                                                                                                                                                                                                                          |
| ------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `startTimer` | <p>Starts the timer in a Timer/SLA field. For example, <code>!startTimer timerField=timetoassginment</code>. This command can also be used to restart a paused timer.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>Timer/SLA fields are not started automatically when an incident is created unless run in a playbook.</p></div>            |
| `pauseTimer` | Pauses the timer in a Timer/SLA field. For example, `!pauseTimer timerField=timetoassignment`. Use this command when a Timer/SLA field has started.                                                                                                                                                                                                                                                                  |
| `stopTimer`  | <p>Stops the timer in a Timer/SLA field. For example, <code>!stopTimer timerField=timetoassignment</code> .After a Timer/SLA field is stopped, you can only reset a timer using the <strong>resetTimer</strong> command.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>Timers are automatically stopped when an incident is closed.</p></div> |
| `resetTimer` | Resets a timer in a Timer/SLA field, which resets the elapsed time, and the status of the timer for the incident. This command should be used to enable a timer that was stopped. For example, `!pauseTimer timerField=timetoassignment`.                                                                                                                                                                            |

{% hint style="info" %}

### Note

When running the commands, you can specify the `incidentID` to change the timer for a different incident.
{% endhint %}


---

# 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/cortex-xsoar-8-on-prem/8.7/configure-cortex-xsoar/slas/use-sla-and-timer-field-commands-manually-in-the-cli.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.