> 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-start-schedule.md).

# Directory Start Schedule

The **Directory Start Schedule** feature allows administrators to configure automatic start times for **AutoStop WorkSpaces** within specific directories. To begin, select a directory from the list on the left. Once selected, the schedule configuration for that directory will appear in the **Schedule Details** panel on the right.

<figure><img src="https://1977539604-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5qADNWBPym2Zh4ZaguCE%2Fuploads%2FZn29XPU5xSVBDgh5ru1S%2Fdirectorystart.png?alt=media&amp;token=f2e0ea9e-739e-4d63-afba-04b7ddb70be0" alt=""><figcaption></figcaption></figure>

Administrators can enable the schedule and configure how often it runs by selecting a **Frequency** of **Daily, Weekly,** or **Monthly**, along with the desired **Start Time (UTC)**.

When the schedule runs, all eligible **AutoStop WorkSpaces** in the selected directory will be automatically started. The **Temporary AutoStop Timeout** setting temporarily overrides the default AutoStop timeout for the specified number of hours. After this period expires, the WorkSpaces automatically revert to the global AutoStop timeout configuration.

{% hint style="danger" %}
Do not schedule start times between **23:30 and 01:30 (local server time)**, as the nightly global AutoStop routine runs during this period.
{% endhint %}

Selecting **Save** applies the schedule to the chosen directory. Only **AutoStop WorkSpaces** are affected by this schedule.

{% hint style="info" %}
**Always On WorkSpaces** are not modified.
{% endhint %}


---

# 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-start-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.
