> 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/managing-rollouts.md). # Managing rollouts Review rollout progress, investigate exceptions, and choose the next safe action. 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. ### When to use this page Use this page when you need to: * confirm a rollout actually started * understand whether download or install work is still moving * decide whether the next action is monitor, extend, or modify ### 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](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts) * [Manage rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/manage-rollouts) * [Schedule rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts) ### 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 ### Review rollouts in this order Use this order to avoid missing the root cause: 1. confirm the rollout exists and targets the intended scope 2. confirm the rollout state matches the current schedule window 3. review failed or incomplete work before you resubmit anything ### What to check first Start with these questions: * did the rollout start at the expected time * is the rollout affecting the intended device or batch set * do failures point to one device group or a broader issue Record the rollout name, batch, expected target count, and schedule window. Use this baseline when comparing progress or investigating exceptions. ### 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 ### Common rollout outcomes Use these checks to interpret what you see: * **The rollout is active** — continue monitoring until devices move to a completed state * **The rollout is complete** — confirm the intended devices received the expected package or change * **The rollout is incomplete or failed** — review the affected device set before you extend or reschedule ### Choose the next action Use the rollout state to decide what happens next: * **Within its schedule window** — keep monitoring. * **Complete with the expected scope** — record the result. * **Unexpected or incomplete** — investigate the affected devices first. Do not submit a duplicate rollout while the original rollout needs review. ### Common problems to check Use these checks to narrow the issue: * **The rollout never started** — confirm the schedule window and the target scope * **Some devices completed and others did not** — compare the affected devices by model, status, or connectivity * **The rollout is still running longer than expected** — confirm devices are checking in and still eligible for the rollout * **You need to change the rollout** — use the modify flow instead of creating a duplicate rollout * **The scope is unexpected** — stop follow-up changes and verify the rollout and batch selection ### Related rollout tasks Use these pages based on what you need to do next: * [Create a batch rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-batch-rollout) — create a rollout for multiple devices * [Create rollout for a single device](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-rollout-for-a-single-device) — create a rollout for one device * [Create a new batch for rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/create-a-new-batch-for-rollout) — extend an existing rollout * [Modify existing rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/modify-existing-rollout) — update a saved rollout or cancel a rollout in progress * [Monitor estate-wide rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/monitor-estate-wide-rollouts) — 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](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/monitor-estate-wide-rollouts) * [Schedule rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts) * [Modify existing rollout](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts/modify-existing-rollout) --- # 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/managing-rollouts.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.