> 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.13/configure-cortex-xsoar/jobs/create-a-time-triggered-job.md). # Create a time triggered job Time triggered jobs run at predetermined times. You can schedule the job to run at a recurring time or one time at a specific date and time. For an example, see the [Create jobs to process indicators example](/cortex-xsoar-8-on-prem/8.13/configure-cortex-xsoar/jobs/create-jobs-to-process-indicators-example.md). 1. Select **Jobs** → **New Job**. 2. Select **Time triggered**. 3. If you want the job to repeat at regular intervals, select **Recurring** and select the desired interval. You can choose to run the job every X number of days, on specific days of the week, at a specific time and also choose a start date and an expiration date. You can configure the recurring job using a cron expression. To do so, after selecting the **Recurring** checkbox, click **Switch to Cron view** and enter the expression. For help defining the cron expression, click **Show cron examples** after switching to cron view.

Note

To view a human readable description of a cron schedule for an existing job, click settings-wheel.png and select Job Schedule from the available columns.

4. If you do not want the job to repeat, **Select date and time** for the job to run. 5. Add or create any relevant tags to use as a search parameter in the system. 6. In the **BASIC INFORMATION** section, add relevant time triggered job parameters. | 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. | 7. Enter any relevant custom field parameters. All fields that have the **Add to all incident types** checkbox selected appear in incident and indicator fields. 8. In the **QUEUE HANDLING** section, select one of the following response options to use if the job is triggered while a previous run of the job is active: * Notify the owner * Don’t trigger a new job run * Cancel the previous job run and trigger a new job run * Trigger a new job run and execute concurrently with the previous run

Important

We recommend to avoid triggering a job while a previous run of the job is active by configuring the playbook a job triggers to close the investigation before running a new instance of the job.

9. Select **Create new 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 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.13/configure-cortex-xsoar/jobs/create-a-time-triggered-job.md?ask=&goal= ``` `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.