> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/other-information/scheduled-upgrade-and-maintenance-periods.md).

# Scheduled upgrade and maintenance periods

Phocas regularly performs scheduled maintenance to keep our system in top shape. This is typically one of the following types of maintenance:

* **System maintenance** such as security patching, to support the availability, stability and performance of the infrastructure behind Phocas
* **Upgrades** releasing the latest version of Phocas to customers, to provide new or enhanced features and functionality and bug fixes.

During periods of scheduled maintenance Phocas is temporarily unavailable. We endeavour to keep the impact of this maintenance to a minimum and in most cases you may only experience a brief disruption.

Please refer to our [status page](https://status.phocassoftware.com/) for details on upcoming scheduled upgrade and maintenance periods.

If you have any questions please contact your Phocas Account Manager.


---

# 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.phocassoftware.com/other-information/scheduled-upgrade-and-maintenance-periods.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.