> 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/10.2-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 can set up specific times on the server to block the running of schedules, which helps you 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.
2. Click the **Create Blockout Time** button.

   The Blockout Time dialog box appears.

   ![New Schedule Blockout Time dialog box](https://591371677-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFgwF7oC7Y6b7XWdahykf%2Fuploads%2Fgit-blob-e783a19332ffe876492d30d6048c9b9692358590%2FssBaservNewSchedBlockTime.png?alt=media)
3. Enter values in the **Recurrence**, **Start Time**, and **Duration** or**End Time** fields to block out specific times.
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.

Your blockout time is set up and no schedules will run on the Pentaho Server during that time. Anyone can 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pba/10.2-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports/manage-schedules/prevent-scheduling-by-setting-blockout-times.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
