> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-cloud/deployments/update-rings/progression.md).
# Update Ring Progression in Patch My PC Cloud
*Applies to: Patch My PC Cloud*
If your Patch My PC (PMPC) Update Rings are configured with longer delays, a new version of a product may be released while an older version is still moving through the rings.
This is not a problem, as when a newer version becomes available, PMPC Cloud does not restart or override the Update Ring process already in progress.
Each version of the software must complete the full Update Ring lifecycle independently. In other words, version *n* will finish all rings exactly as configured, and version *n+1* will follow the same path when its turn begins.
The diagram below illustrates how each version progresses through the rings independently.
{% hint style="info" %}
**Note**
See the [Patch My PC Update Rings: Mastering Phased Rollouts in Intune | Tips for a Better User Experience](https://www.youtube.com/watch?v=jgfErZIzNhQ) on our YouTube channel for more details.
{% endhint %}
## Update Rings forecast
To help you predict how your Update Rings will progress, we provide a [PowerShell script](https://github.com/PatchMyPCTeam/Community-Scripts/blob/main/Other/Reports/Get-UpdateRingForecast.ps1) that generates an HTML report. This report gives you a clear visual overview of your current Update Rings configuration and how each ring is expected to advance.
{% hint style="info" %}
**Note**
See the [Update Ring Forecaster](https://www.youtube.com/watch?v=RelJPqWIGno) on our YouTube channel for a detailed walkthrough of the script and the report.
{% 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://docs.patchmypc.com/patch-my-pc-cloud/deployments/update-rings/progression.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.
