> For the complete documentation index, see [llms.txt](https://help.depence.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.depence.com/depence-hardware/modules/scheduler/year-schedule.md).

# Year Schedule

![](https://content.gitbook.com/content/SJPsyh5CBOise9BtVNGO/blobs/Qf3bHsZ6hFJzfRHiDyaK/image.png)

Create a new year schedule by adding a new year schedule in the listing of the Year Schedule area after right-clicking. Enter the current year as the name. For example 2021\
Now double-click on the corresponding year plan to load it into the year plan editor.

You can now drag and drop weekly plans and daily plans onto any day in the plan.

The green blocks are weekly plans and the yellow blocks are daily plans.

The Logic.\
When the scheduler starts, it looks backwards in the calendar from the current date until it finds a weekly schedule. Then it´s executed and the daily schedule is started on the current day of the week (for example Wednesday). This is repeated day by day until a date is occupied with a daily schedule. This daily schedule now has priority and is executed on this one day. On the next day, the last weekly schedule is searched for and executed.


---

# 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://help.depence.com/depence-hardware/modules/scheduler/year-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.