Start free

Held back or rolled back: what it means

The difference between an update that was held back and one that was rolled back, and what to do next.

Held back

The update failed on the test copy, so nothing went live. Your live site was not touched. You see what failed, what it means, the likely cause, what you can do and whether Verploy retries.

Rolled back

The update went live, a problem was found after going live, and Verploy restored the site from the snapshot taken just before. It only counts as rolled back after the tested pages were reloaded and the installed versions were compared.

On sites with the data guard, orders, form submissions, comments and user accounts created after the backup stay on the site.

What to do next

  1. Open the update and read the explanation.
  2. Follow the suggested next step, for example update PHP first or check the licence.
  3. For a change that is only visual, see approve a visual change.

Related articles

Approve a visual change, or test onlyWhen a theme or page-builder update only changes how pages look, approve it with one click. For big updates, use Test only.Premium plugins and licencesWhy a premium update can be missing, how to fix the licence, and how to install a new version with a ZIP upload.Choose how updates are madeAsk first, update automatically, or never automatically: how the update policy and the smart update rules work.

Still stuck? Email us at team@verploy.com with the site and what you see. We answer in English or Dutch.

Email team@verploy.com
Help center
System status