> 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/edit-a-schedule.md).

# Edit a Schedule

You can edit a schedule to change the frequency of the scheduled report, report parameters, and email settings.

1. Click the **Home** drop-down menu on the upper-left and click the link to the **Schedules**.

   The list of schedules appears in the Schedules page.
2. Click the schedule you want to edit in the list, then click **Edit** in the scheduling toolbar.

   The Edit Schedule window appears.
3. Type to rename the schedule in the **Schedule Name** field.
4. Choose a new time interval for the report from the **Recurrence** list.
5. Choose a new **Start Time** and **Recurrence Pattern**, as well as new **Start** and **End by** dates for the schedule. Click **Next**.

   If blockout times have been scheduled by your administrator, a **View Blockout Times** button appears on the bottom of the New Schedule window. A list of blockout times is viewable by clicking **View Blockout Times**.
6. Choose what type of file you would like the schedule to create from the **Parameters** field. Click **Next**.

   The email option will only appear if your system administrator has enabled email on the server.
7. Click **OK**.

The schedule is edited and appears in the list in the Schedules window of the console.


---

# 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/9.3-analytics/pentaho-user-console/about-pentaho-user-console-perspectives/schedules/schedule-reports/edit-a-schedule.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.
