> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/rollouts/monitor-estate-wide-rollouts.md).

# Monitor estate-wide rollouts

Review rollout status and batch progress across the estate.

Use this page to monitor scheduled rollouts across the estate.

### When to use this page

Use this page after you create a rollout and need to track its progress.

Use it to review current rollout status, inspect batches, and decide whether follow-up action is required.

### View current rollouts

1. Go to **Verifone Central** → **Device Management** → **Rollouts**.
2. Review the current rollout list.
3. Expand a rollout to review its batches and status details.

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/dzivQyj8aHN5Kvmx8apX/blobs/Y8wszWnqwYTjB7gT4szV/image.png" alt=""><figcaption></figcaption></figure></div>

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/dzivQyj8aHN5Kvmx8apX/blobs/p438VfavhAjoJAsX9EIW/image.png" alt=""><figcaption></figcaption></figure></div>

### Triage a rollout

Review each rollout in this order:

1. Match the rollout and batch names to the deployment plan.
2. Compare its status with the scheduled download or install window.
3. Isolate affected devices before changing or rescheduling anything.

Use [Modify existing rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/modify-existing-rollout) only after you confirm the rollout state.

### What you can monitor

Use the rollout view to track:

* single-device rollouts
* multi-batch rollouts
* rollouts saved for later

### What to check

When you review the rollout list, confirm:

* which rollouts are active
* whether any batch needs attention
* whether the rollout you expect is progressing, saved, or blocked

Compare status with the rollout name, batch, target count, and schedule window. This separates expected waiting from a rollout that needs investigation.

### Verify the result

After you review the page, confirm that:

* the rollout list shows the expected rollout and batch entries
* the status information is enough to decide the next action
* you know whether to continue monitoring, edit a saved rollout, or investigate a failure
* any exception is assigned to the correct rollout and batch
* the next action has an owner: continue monitoring, modify, or investigate

### Related pages

* [Managing rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/managing-rollouts) — review rollout actions and state changes
* [Rollout dashboard KPIs](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/monitor-estate-wide-rollouts/rollout-dashboard-kpis) — interpret rollout counts and success rate


---

# 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.verifone.com/verifone-central-getting-started/verifone-central/verifone-central-device-manager/rollouts/monitor-estate-wide-rollouts.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.