Update failures
A round rolled back, a plugin was refused, or verification failed.
The round rolled back
A round rolls back when its checks fail after the updates: the front page or the admin did not answer, or a regression page changed beyond its threshold. The round's record says which check and what it found. The site is back on the versions it had before the round; nothing further is needed for the site. What to do about the update itself depends on the cause — a page that changed because of a legitimate redesign in a theme update needs its threshold reconsidered or a new baseline; a plugin that breaks the site needs the plugin's author.
A plugin was refused
Each plugin update in a round records the worker's own reason. The ones that recur:
| Reason | Meaning | Retried? |
|---|---|---|
| licence required, empty package url | a premium plugin whose licence is missing or expired on the site | no — the same refusal would come back, and the customer would be told three times |
| custom updater issue | the plugin updates through a mechanism WordPress's updater cannot drive | no |
| download failed | the package could not be fetched at that moment | yes, up to three attempts |
| anything else | an unrecognised refusal | yes — declining a retry that would have worked costs the update; making a pointless one costs a request |
A refusal that is not retried is recorded as not retryable, separately from gave up: one attempt was spent and the cause named, against three attempts exhausted.
"Verification failed"
The worker said it updated the plugin and the site does not show the new version. The platform records that as a verification failure, never as a success. Usual causes: a page cache answering for the site, or a plugin whose reported version does not change on update. Sync the plugin list and compare.
The round ended unexpectedly
The round stopped without writing an outcome: the platform's work on it was interrupted. The site is taken out of maintenance mode by the worker's own deadline if the platform did not manage it. Check the site, then run the round again.
The round would not start
The dashboard says why: the worker is older than the version that brings a site back on its own, the site is unreachable, or another operation holds the site. The first is fixed by the worker's rollout reaching the site; the platform asks the site for its version rather than reading what it last reported. Compatibility.
A scheduled round did not run
Rounds run on the package's frequency on the site's update weekdays, checked hourly. A site whose worker is too old, or that is unreachable, is skipped and the reason recorded.