> 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-xsiam/configure-cortex-xsiam/customize-cases-and-issues/customize-issue-fields-and-layouts/issue-fields/user-issue-timer-field-commands-manually-in-the-cli.md). # Use issue timer field commands in the CLI Use Cortex XSIAM CLI commands to set, start, pause, stop, and reset issue timer fields and SLA targets. You can manage the timers for a specific issue by running commands manually in the CLI. By running CLI command you can to manage timers on a more granular level within specific issues when the need arises. For example, for a high severity issue you might need to decrease the response time.
Set timer fields in Cortex XSIAM Use the `setIssue` command to set a specific issue due date, or to set a specific timer field in an issue. If you add the `sla` parameter to the command, it sets the time for the issue's due date. If you also add the `slaField` you set the timer for the issue field. To change the Time to Assignment field target to 30 minutes in the current issue, run the following command: ``` !setIssue sla=30 slaField=timetoassignment ``` To change the timer to February 1, 2024, at 11.12 am, run the following command: ``` !setIssue sla=2024-02-01T11:12 ``` {% hint style="info" %} 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 issue field. {% endhint %}
Start or stop timer fields in Cortex XSIAM Run the following commands in the CLI:
CommandDescription
startTimer

Starts the timer.

This command can also be used to restart a paused timer.

!startTimer timerField=timetoassignnment


Timer fields are not started automatically when an issue is created unless run in a playbook.

pauseTimer

Pauses the timer.

Use this command when a timer field has already started.

!pauseTimer timerField=timetoassignment


stopTimer

Stops the timer.

!stopTimer timerField=timetoassignment


After a timer field is stopped, before you can start the timer again you must reset the timer using the resetTimer command.

Timers are automatically stopped when an issue is closed.

resetTimer

Clears all fields for the timer.

This command must be used before restarting a timer that was stopped.

!resetTimer timerField=timetoassignment


{% hint style="info" %} When running commands in the CLI, you can specify the `alertID` to change the timer for a different issue. {% 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 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-xsiam/configure-cortex-xsiam/customize-cases-and-issues/customize-issue-fields-and-layouts/issue-fields/user-issue-timer-field-commands-manually-in-the-cli.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.