Understanding Results
Every update attempt ends with a result. You see it in the Extensions list, in Activity, in Logs and in the emails.
Every update attempt ends with a result. You see it in the Extensions list, in Activity, in Logs and in the emails.
| Result | Meaning | What to do |
|---|---|---|
| Updated | Installed, and the checks passed. | Nothing. |
| Updated, with "The extension's install script reported: …" | The new version is installed, but the extension's own install script reported an error at the end. | Read the message and check the extension. |
| Download failed | The update server could not be reached, or answered with an error. | Usually temporary. AutoPilot tries again on the next runs. |
| Download refused (licence) | The server refused the download, or sent a web page instead of a package. Typical for paid extensions with a missing or expired download key. | Enter or renew the key under System → Update Sites. |
| Checksum mismatch | The package does not match the checksum its developer published. It was not installed. | Try again later. If it keeps happening, contact the developer. |
| Snapshot failed | The snapshot could not be created, so the update was not installed. | Check System health and the free disk space. |
| Install failed | Joomla's installer or the extension's install script refused the package. The old version stays. | Read the message. It usually names the cause, for example a missing PHP extension. |
| Verification failed | Installed, but a check after the update failed. | Look at the site. Roll back, or dismiss the warning if all is well. |
| Awaiting approval | Waiting in Approvals. | Approve or reject it. |
| Skipped (outside maintenance window) | Not inside the window at the time of the run. | Nothing. It is tried again. |
| Skipped (delay) | The delay has not passed yet. | Nothing. |
| Skipped (pinned) | The version pin does not allow this version. | Change the pin if you want the update. |
| Skipped (incompatible) | The update needs a newer Joomla or PHP version. | Update Joomla or PHP first. |
| Skipped (policy) | Another rule held it back, most often auto-update being off. | Turn auto-update on, or update by hand. |
| Skipped (not supported) | The extension has no standard update server. | Update it by hand. |
| Skipped (failed too often) | This version failed on several runs in a row, and scheduled runs have stopped trying it. | Fix the cause, then update the extension by hand. See When an update keeps failing. |
| Already up to date | The update was no longer needed when its turn came, for example because someone installed it by hand. | Nothing. |
| Rolled back | A snapshot was restored. | Nothing. |
| Rollback failed | A restore did not finish. | Open Logs for the run. Try again, or use Emergency recovery. |
When an update keeps failing
A scheduled run tries a failed update again on its next turn. That is right for a server that was down for an hour, and pointless for a licence key that is missing: the same update would fail every day.
Settings → Retry Failed Updates sets how often that happens. With the default of 3, a version is tried on four runs: once, and three more times. If it failed every time, AutoPilot stops and records Skipped (failed too often) once, with the number of failures. The extension keeps its last real result, for example Install failed, so it stays under Failed in the Extensions list. Each failed attempt sends the Update Failed email; the skip does not, and the Dry run shows it with its reason.
After that the version is tried again only when:
- you update the extension by hand (Update in its row). A manual update is always tried, so this is how you start over once the cause is fixed, for example after entering the download key;
- a newer version appears. Every version gets its own attempts;
- you raise the number in the Settings.
The other extensions of a run are not affected.