> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/upgrade-to-cortex-xdr-5/early-upgrade-with-flexible-scheduling.md).

# Early upgrade with flexible scheduling

The upgrade to Cortex XDR 5 follows our standard version release process. If the upgrade option is presented in your tenant, you can experience the new features ahead of the standard rollout by initiating the upgrade directly from your tenant. Here's how it works:

* When logging into a tenant, instance administrators and account administrators will see a pop-up notification about the available upgrade. From this notification, you can either initiate the upgrade immediately or schedule it for a later time. If you schedule the upgrade, it will run automatically at your chosen time.
* During the upgrade your tenant will be temporary unavailable.
* An additional notification will appear in the **Notification Center**, where you can view upgrade details, edit the scheduled timeframe or cancel the upgrade as needed.

{% hint style="info" %}

### Note

* This offering is available for eligible customers. Detailed information will be shared prior to the upgrade. Please contact your account representative for more details.
* The option to schedule your upgrade will be available for a limited time. After this date, any tenants that haven't been upgraded will be included in the standard quarterly release cycle.
* You can upgrade from Monday to Thursday, between 05:00 and 17:00 UTC. This schedule avoids our reserved maintenance hours.
  {% 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://cortex-docs.paloaltonetworks.com/upgrade-to-cortex-xdr-5/early-upgrade-with-flexible-scheduling.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.