> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/changelog/2026/readme.md). # October 2026 {% hint style="success" %} **Please note** that the release notes usually receive updates in the second week of the following month (*e.g. August gets published in mid September*), hence this document is not yet showing all released features and improvements. {% endhint %} ### New features and improvements * 🎉 **Support hours now cover ranges across the week**: a night shift from Tuesday 22:00 to Wednesday 06:00, or a whole weekend from Friday 17:00 to Monday 09:00, is one range instead of a window cut off at midnight. **Office hours**, **Outside office hours** and **24/7** presets fill the editor in one click, a **Right now** badge shows whether a support hour is in hours and until when, and every support hour is drawn as a week chart in the list, on its page and in the editor * Holidays imported into support hours now cover the **whole day**, from `00:00` to `00:00` the next day, instead of ending at `23:59` * An event flow that holds events in a **Wait** node until a support hour starts or ends now counts as using that support hour: it is listed under **Used in** and stops the support hour from being deleted * The API's support hours gained `supportWindows` for ranges across the week and `include=currentStatus` for whether a support hour covers this moment. Clients that only send `supportDays` keep working, and the Terraform provider manages ranges as `support_windows` on `ilert_support_hour` from version 2.29.0 {% embed url="" %} --- # 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.ilert.com/changelog/2026/readme.md?ask=&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.