> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports/manage-schedules/prevent-scheduling-by-setting-blockout-times.md).

# Prevent Scheduling by Setting Blockout Times

From the Pentaho User Console, you set up specific times on the server to block the running of schedules, which allows you to perform administrative functions such as system maintenance or managing server traffic during peak usage times.

1. From the User Console **Home** menu, click **Schedules**

   The Schedules page appears.

   ![Blockout Times dialog box](/files/4eEf7v2bUEZDjpgVRh6t)
2. Click the **Create Blockout Time** button or the green Plus Sign (+) in the **Blockout Times** tool on the left side of the Schedules screen.

   The Blockout Time dialog box appears.

   ![New Schedule Blockout Time dialog box](/files/JRF6S0UwWmuOyulogPVq)
3. Enter values in the **Recurrence**, **Start Time**, **Duration** or**End Time**, and **Start Date** fields for the blocked out time.
4. Click **OK**. If **Run Once** is selected in the **Recurrence** field, a dash displays under the **Start Time** and **End Time** fields in the blockout list, until the blockout time passes.

The Blockout Time is created and no schedules will run on the Pentaho Server during that time. Users are able to view a list of blocked out times when they are creating schedules.


---

# 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://docs.pentaho.com/pba/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports/manage-schedules/prevent-scheduling-by-setting-blockout-times.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.