> 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.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/jobs/time-triggered-job-parameters.md).

# Time Triggered Job Parameters

Describe parameters for creating a time-triggered job in Cortex XSOAR 6.15.

The following table describes the job parameters when creating a time triggered job.

| Name        | Description                                                             |
| ----------- | ----------------------------------------------------------------------- |
| Name        | Enter a meaningful name for the job.                                    |
| Owner       | Assign an owner to the incident.                                        |
| Role        | Select the role who can access the incident.                            |
| Type        | Determine the incident type created by this job.                        |
| Severity    | Determine the severity of the incident that is created.                 |
| Playbook    | Determine which playbook to run when this job is triggered.             |
| Labels      | Select the labels that are available in the incident type.              |
| Phase       | Select the phase of the investigation in which this incident is opened. |
| Details     | Add details that should appear within the incident.                     |
| Attachments | Add attachments to the job.                                             |


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/jobs/time-triggered-job-parameters.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.