Known site problems are not retried (2.37.0). When an update cannot be installed on a site for a reason the site has to fix first — a licence that is not active, no download file from the plugin’s maker, a PHP or WordPress version that is too old, not enough disk space for the test copy, a firewall that blocks Verploy — Verploy now says so once and does not start that update again, not at night and not when you click. The site page shows “Not available” with the one thing to do, and the inbox shows what it is waiting for and who can fix it. As soon as something changes — a new version from the maker, the licence activated, PHP updated by your hosting provider, a passed connection check — the update runs again by itself. If you want to try anyway, “Try anyway” is one click away.
Faster small plugin updates (2.35.0). A small update of a plugin from WordPress.org — same major version, at least seven days out in the open or live elsewhere without trouble, and never failed on a Verploy site — now goes live without a test copy: snapshot first, then the update, then the same checks on the live site and automatic rollback if anything is wrong. Themes, page builders, WordPress core, premium plugins, shop and payment plugins and webshops always keep the test copy. The run page says which route was taken.
A green test copy is enough (2.35.0). When an update passes every check on the test copy, it goes live, also at night. Softer signals that used to hold updates back on their own, such as a failure on another site or an earlier failed attempt, no longer do. A failed check still holds an update back.