> 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.13/learn-about-cortex-xsoar/customize-and-configure-cortex-xsoar/reports/schedule-a-report.md). # Schedule a report You can schedule a report to run at specific times with start and end dates. You can also add restrictions on the report content and the number of recipients. If you want to send the report to users by email, you need to add an email integration instance, such as EWS, Gmail, Mail Sender, and so on. 1. In the **Reports** tab, select the report you want to schedule. 2. In the **Next Run** field, click **Disabled** or the date it was last run. If creating or editing a report, click next to the **Schedule** field. 3. In the dialog box, add the following information: * The email addresses of the recipients you want to send the report to, if required. * Select the **Scheduled** checkbox. 4. If you want to restrict the content of the report according to roles, in the **Run as Roles** field, from the dropdown list, select one of the roles. If there are roles with conflicting permissions, the highest permission level takes precedence. After you select a role, users with lower permissions than that role are not able to edit the report. For example, if you set **Run as Roles** to Administrator, Analysts do not have edit access to the report. 5. Schedule a report according to one of the following methods: * **Human view**: Schedules a report according to the set number of hours. You can add days of the week with start and end times. When scheduling a report in the **Human view** the **Next Run** date may be incorrect. You may need to change the number of hours field when scheduling the report. * **Cron view**: Schedules a report according to a Cron time string format, which consists of five fields that Cron converts into a time interval. Use this view to schedule a report on certain hours, days, months, years, and so on. For examples of Cron strings, see [Schedule a Report Examples](#UUID-d4b6df2c-b78e-a369-7cae-d0ebae55c73e).

Note

When using the Cron view, the Start at and Ends fields may conflict with Cron string expressions. For example, when using frequencies (i.e. ‘/’) if you type the expression 0 */6 * * * (runs every 6 hours), with a start time of 15.00, the next run time is not 21:00. The run time depends on Cron run times, which are 00.00, 06:00, 12:00, and 18:00 per day. In this example, the report runs at 15.00, 18.00, and then 00.00, etc. For examples using Cron generally, see Cron examples.

6. Click **Save**. The schedule date appears in the **Next Run** field on the main **Reports** tab. ### **Schedule a Report Examples** The following examples describe how to schedule a report using the Cron scheduler format. The Cron time string format consists of five fields that Cron converts into a time interval. For example, a Cron string of **`0 10 15 * *`** runs a report on 15^(th) of each month at 10:00 AM. #### **Schedule a report starting January 1 and then monthly** In this example, you want to schedule a report for January 1, 2020 at 8:00 AM, and thereafter on the 1^(st) of each month. In the **Cron Expression** field, type **`00 8 1 1/1 *`** | Number | Description | | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 00 | 00 in minutes | | 8 | 8 AM | | 1 | The first of each month | | 1/1 | Starting in January, and every month thereafter. If you want the report to start in a different month, change 1/1 to the relevant month, such as 2/1 for February, 3/1 for March and so on. | | \* | Any day of the week | The reports run at 8:00 AM on January 1, 2020, February 1, 2020, March 1, 2020, and so on. {% hint style="info" %} ### Note Cron calculates the next relevant date. If you want the report to run next month, provided that date has passed in the current month, you do not need to specify the month. For example, assume the date is December 12. To run the report on January 11 at 8:00 AM, type **00 8 11 \* \***. The report starts running on January 11 (and on the 11^(th) of each month, thereafter). If the current date is December 10, the next run date would be December 11. {% endhint %} #### **Schedule a report for once a year** In this example, you want to schedule a report for January 1, 2020 at 8:00 AM, and every year on January 1 (the current date is Thursday, December 12, 2019). In the **Cron Expression** field, type **`00 8 1 1 *`** | Number | Description | | ------ | -------------------------------------------------------------- | | 00 | 00 minutes | | 8 | 8 AM | | 1 | 1st day of each month | | 1 | Starting every January. For different months change the number | | \* | Any day of the week | The report runs at 8:00 AM on January 1, 2020, January 1, 2021, January 1, 2022, and so on. #### **Schedule a report every week on a Monday** In this example, you need to schedule a report to run at midnight every week on a Monday (the current date is Thursday, December 12, 2019). Type the following expression in Cron: **`00 0 * * 1`** | Number | Description | | ------ | ------------- | | 00 | 00 in minutes | | 0 | Midnight | | \* | Any day | | \* | Any month | | 1 | Monday | The report runs on the first available Monday, which is December 16 at midnight, and then on December 23, December 30, January 6, and so on. #### **Schedule a report every weekday from February for 6 months** In this example, you need to schedule a report at 5:30 PM every weekday (Mon–Fri) starting in February for 6 months (assume the current date is Thursday, December 12, 2019). In the **Cron Expression** field, type **`30 17 * 2/6 1-5`** | Number | Description | | ------ | ------------------------------------------ | | 30 | 30 minutes | | 17 | 5 PM | | \* | Any day | | 2/6 | Starting in February for the next 6 months | | 1-5 | Monday to Friday | The report runs at 5:30 PM on February 3, 4, 5, 6, 7, and so on. #### **Schedule a daily report** In this example, you need to schedule a report every day at 6:00 AM (the current date is Wednesday, December 12). In the **Cron Expression** field, type **`0 6 * * *`** | Number | Description | | ------ | ---------------------------------------------------------------------------------------------------------- | | 00 | 00 in minutes | | 6 | 6 AM | | \* | Any day | | \* | Any month | | \* | Any day of the week. If you want to run from Monday to Friday, type 1-5. For Sunday to Thursday, type 0-4. | The report runs at 6 AM on December 13, 14, 15, 16, and so on. --- # 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.13/learn-about-cortex-xsoar/customize-and-configure-cortex-xsoar/reports/schedule-a-report.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.