> For the complete documentation index, see [llms.txt](https://docs.dispel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dispel.com/changelog/earlier-releases/2024-10-03.md).
# 3 October 2024
Fall 2024 Infrastructure Updates
## 3 October 2024
{% hint style="info" %}
Published on dispel.com.
{% endhint %}
## Fall 2024 Infrastructure Updates
As part of our ongoing efforts to enhance the performance, security, and scalability of our systems, Dispel is undergoing a comprehensive update to all infrastructure during Fall 2024. These updates will ensure that our systems remain robust and can support the addition of future features and services, while continuing to maintain the highest standards of security.
### Key Takeaways of the Update
* Security Enhancements:
Routine security updates to ensure the highest possible security standards are being maintained.
* Dependency Upgrades & Infrastructure Improvements:
Preparing all infrastructure to communicate with an updated orchestration engine to facilitate future features.
### Impact on Services
These updates are designed to require minimal changes from our customers. However, because downtime will be required, a small outage window is being scheduled for each deployment during low-traffic periods to minimize disruption. These windows are communicated and agreed upon with customer points of contact well ahead of the update.
For more information on Maintenance Windows, please visit
---
# 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.dispel.com/changelog/earlier-releases/2024-10-03.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.
