> 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.14/investigate-and-respond-to-threats/incidents-and-indicators-investigation/investigate-an-incident/schedule-a-command-in-the-war-room.md).

# Schedule a command in the War Room

You can run a scheduled command once or on a recurring schedule, setting the start time, end time, and frequency. Some common use cases for scheduling a command:

* Mirroring a ticket from an external ticketing system.
* Sending an email to a user, waiting a determined amount of time, and then sending the email again if a response has not been received.

{% hint style="info" %}

### Note

Scheduled commands run using the tenant's timezone.
{% endhint %}

1. Open an incident, locate the command entry in the War Room, and click the clock icon.

   ![](/files/oQKIPrutmFrjSGy36VuR)

   By default, scheduling options are displayed in a human-readable view. For recurring commands, you can use either a human-readable view or switch to the Cron view.
2. To schedule a command using the human-readable view:
   * For a non-recurring command, set the date and time for the command to run.
   * For a recurring command, select **Recurring** and then set the frequency.
3. To schedule a recurring command using the Cron view:
   1. Select **Recurring**, and then click **Switch to Cron view**.
   2. Define the Cron expression.
      * Expand **Show cron examples** to view sample schedules in Cron format.
      * Set a start date and time.
      * (Optional) Set an end date and time.
4. Save the Schedule.

To remove a scheduled command, click the clock icon and then click **Remove schedule**.

You can also schedule commands to run in the War Room by using a script. For more information, see the [ScheduleCommand](https://xsoar.pan.dev/docs/reference/scripts/schedule-command) script.


---

# 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.14/investigate-and-respond-to-threats/incidents-and-indicators-investigation/investigate-an-incident/schedule-a-command-in-the-war-room.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.