> For the complete documentation index, see [llms.txt](https://docs.itconductor.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/general/maintenance-mode/scheduled-maintenance.md). # Scheduled Maintenance ### How to Schedule a Single System Into Maintenance Mode 1. Navigate to the IT-Conductor Service Grid and find the container group to update. 2. Click on the context menu icon (i.e. SAP logo) for that group. 3. Click **Event Schedule**.

Figure 1: Event Schedule for a Single System

4\. In the "Scheduled Maintenance Events" pop-up window, click the "Maximize" button.

Figure 2: Scheduled Maintenance Events

5\. Click the "Create new maintenance event" button.

Figure 3: Create New Maintenance Event

6\. Fill out the fields, especially the Start and End Dates and Times. Then click **Finish**.

Figure 4: New Maintenance Event

7\. The newly created event schedule will be in "Waiting" status until it gets triggered. 8\. Once it gets triggered and the set schedule date and time have gone by, the status will change to "Succeeded".

Figure 6: Event Schedule in Succeeded Status

### How to Schedule Multiple Systems Into Maintenance Mode 1. Navigate to the Service Grid and find the container group (i.e. SAP Systems) to update. 2. Click on the context menu icon (i.e. SAP logo) for that group. 3. Click **Event Schedule**.

Figure 7: Event Schedule for Multiple Systems

4\. Repeat Steps 4-6 above. Also, expect the same for Steps 7-8. --- # 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.itconductor.com/~/changes/j1RdUn49WBcajmJEmXUf/users-guide/monitoring/general/maintenance-mode/scheduled-maintenance.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.