> 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-device-management/verifone-central/rollouts/managing-rollouts.md).

# Managing rollouts

Review rollout status and follow rollout progress after scheduling.

Use this page when you need to monitor active rollouts, confirm completion, or investigate rollout issues.

### Before you start

Confirm that:

* the rollout has already been created or scheduled
* you know whether you are tracking one device, one batch, or multiple rollout jobs
* the software, parameter, or content package was prepared correctly before scheduling

If you still need to prepare or schedule the rollout, start here:

* [Rollouts](/verifone-central-device-management/verifone-central/rollouts.md)
* [Manage rollouts](/verifone-central-device-management/verifone-central/rollouts/manage-rollouts.md)
* [Schedule rollouts](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts.md)

### What managing rollouts includes

Use rollout management to:

* review rollout progress after submission
* check whether downloads or installs completed
* identify rollouts that need follow-up
* track rollout activity across one device or many devices

### Monitor rollout progress

After a rollout starts, review its status to confirm whether it is progressing as expected.

Track:

* rollout state
* target devices or batches
* current progress
* completed or failed rollout activity

### When to review a rollout

Review rollout status when you need to:

* confirm that a scheduled rollout has started
* check whether the deployment completed successfully
* decide whether another rollout or update is required
* investigate devices that did not receive the expected update

### Related rollout tasks

Use these pages based on what you need to do next:

* [Create a batch rollout](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts/create-a-batch-rollout.md) — create a rollout for multiple devices
* [Create rollout for a single device](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts/create-rollout-for-a-single-device.md) — create a rollout for one device
* [Create a new batch for rollout](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts/create-a-new-batch-for-rollout.md) — extend an existing rollout
* [Modify existing rollout](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts/modify-existing-rollout.md) — update a saved rollout or cancel a rollout in progress
* [Monitor estate-wide rollouts](/verifone-central-device-management/verifone-central/rollouts/monitor-estate-wide-rollouts.md) — review broader rollout activity and status

### Result

You can confirm rollout progress and decide whether more action is needed.

### Next steps

* [Monitor estate-wide rollouts](/verifone-central-device-management/verifone-central/rollouts/monitor-estate-wide-rollouts.md)
* [Schedule rollouts](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts.md)
* [Modify existing rollout](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts/modify-existing-rollout.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verifone.com/verifone-central-device-management/verifone-central/rollouts/managing-rollouts.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.