> 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.12/configure-cortex-xsoar/customize-and-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 [Add Indicators to SIEM Using a Time Triggered Job](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/jobs/add-indicators-to-siem-using-a-time-triggered-job.md). {% hint style="info" %} ### Note To view a human readable description of a cron schedule for an existing job, change the table settings by clicking the Settings icon and selecting **Job Schedule** from the available columns. {% endhint %} 1. Select **Jobs** → **New Job**. 2. Select **Time triggered**. 3. If you want the job to repeat at regular intervals, select the **Recurring** checkbox and choose 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 have the option to 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 assistance in defining the cron expression, click **Show cron examples** after switching to cron view. 4. If you do not want to the job to repeat, **Select date and time** the job should run. 5. Add or create any relevant tags to use as search parameter in the system. 6. In the **Basic information** section, add the required [Time Triggered Job Parameters](/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-configure-cortex-xsoar/jobs/time-triggered-job-parameters.md). 7. Enter any relevant custom fields parameters. All fields that have the **Add to all incident types** checkbox selected in incident and indicator fields, appear. 8. In the **Queue Handling** section, select whether to notify the owner of the job if the job is triggered while a previous run of the job is active.

Note

Notifications are only sent if a mail sender integration is configured. To test your mail integration, from the CLI, run !send-mail to=my-email@my-company.com subject=test body=test.

9. Select an option to use if the job is triggered while a previous run of the job is active: * 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. 10. **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/xsoar-6-administrator-guide/6.12/configure-cortex-xsoar/customize-and-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.