> For the complete documentation index, see [llms.txt](https://docs.nuvens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nuvens.cloud/admin/configuration-section/directory-reboot-schedule.md).

# Directory Reboot Schedule

The **Directory Reboot Schedule** feature allows administrators to configure automatic reboot times for WorkSpaces within specific directories. To begin, select a directory from the left panel. You can then set a default reboot schedule using options such as **Daily**, **Weekly**, or **Monthly**, specify the desired time, and select the appropriate time zone. Once the default schedule is configured click **Save** to apply it to all WorkSpaces in the selected directory.

<figure><img src="https://1977539604-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5qADNWBPym2Zh4ZaguCE%2Fuploads%2FvZUejnHEpH3GSxIJxidq%2Fdirectoryreboot.png?alt=media&amp;token=ab8aa708-4f53-457b-87ec-422f04a7d0bf" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Enabling the **Reboot if Connected** option ensures that WorkSpaces are rebooted regardless of user activity.
{% endhint %}

Under **Workspace Overrides** you'll see a list of individual WorkSpaces within the selected directory. If certain WorkSpaces require a different reboot time you can assign a custom schedule by selecting a new time, enabling the **Override** toggle, and clicking Save. The **Next Run (UTC)** column reflects the upcoming scheduled reboot time for each WorkSpace.


---

# 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.nuvens.cloud/admin/configuration-section/directory-reboot-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.
