For the complete documentation index, see llms.txt. This page is also available as Markdown.
Cortex XSIAM

Create a time-triggered job

Schedule a Cortex XSIAM playbook job to run at a specific time.

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.

Configure your playbook to close the investigation

  1. Select Investigation & Response → Automation → 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.

    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 the date and time for the job to run.

  5. In the BASIC INFORMATION, section, add relevant time-triggered job parameters from the following:

    Name
    Description

    Name

    Enter a meaningful name for the job.

    Playbook

    Determine which playbook to run when this job is triggered.

    Description

    Enter a meaningful description of the job.

  6. 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:

    • 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

    We recommend avoiding 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.

  7. Ensure that the playbook assigned to this job includes the closeInvestigation built-in command as its final execution step. This action closes the underlying container workspace and enables the user interface to show the accurate completion status.

  8. Select Create new job.

Last updated

Was this helpful?