> 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-agentix/configure-cortex-agentix/cases-and-issues-configuration/customize-issue-fields-and-layouts/issue-fields/create-custom-issue-fields/issue-timer-fields.md).

# Issue timer fields

By default, timer fields are disabled in Cortex AgentiX. To enable timer fields, go to Settings → Configurations → General → Server Settings → **Issues** and **Enable Timer Field**.

Timer issue fields provide you with the ability to track reaction time and help you measure issue-level metrics. Timers can measure multiple aspects of an issue. You can, for example, have a timer track how long since the first playbook ran, and have another timer track how long you've been waiting for a user's response. Timers display in the issues table and in issue layouts.

Timer fields can be started, stopped, or paused in a playbook, script, or manually in the CLI.

Timer fields count up from when a specific action or task began and also (optionally) count down from a target. The Risk Threshold tells you when a timer is considered at risk and you can customize the time period for the Risk Threshold.

Timer fields always show the total duration while they are still running. If they are at risk, they show the at risk status. After a timer field has timed out (passed the target), the timer shows both the total duration and how long past the target.

Timer fields do not automatically trigger actions when timers time out. You can configure a script to run when a timer times out.

Scripts

You can run scripts to act on timeouts, such as sending an email when a timeout occurs. You can also make specific changes to an issue field or a parent case issue, such as changing the case owner. Cortex AgentiX includes out-of-the-box scripts or you can create your own scripts. Scripts must have the `SLA` tag to be used for timer fields. For more information, see [Automate changes to issue fields using timer scripts](/cortex-agentix/configure-cortex-agentix/cases-and-issues-configuration/customize-issue-fields-and-layouts/issue-fields/create-custom-issue-fields/issue-timer-fields/automate-changes-to-issue-fields-using-timer-scripts.md).

Using the CLI

If you want to set or change timers for an issue you can use the `setIssue` command in the CLI. You can also use commands such as `startTimer`, `stopTimer`, and `pauseTimer`. For more information, see [Use issue timer field commands manually in the CLI](/cortex-agentix/configure-cortex-agentix/cases-and-issues-configuration/customize-issue-fields-and-layouts/issue-fields/create-custom-issue-fields/issue-timer-fields/use-issue-timer-field-commands-manually-in-the-cli.md).


---

# 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-agentix/configure-cortex-agentix/cases-and-issues-configuration/customize-issue-fields-and-layouts/issue-fields/create-custom-issue-fields/issue-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.