Understanding Results
The same skip is not recorded again on every run, so Activity stays readable. A scheduled run tries a failed update again on its next turn.
| Result | Meaning | What to do |
|---|---|---|
| Updated | Installed. | 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. |
| 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. |
| Skipped (policy) | Auto-update is off for this extension. | Turn it on, or update by hand. |
| Skipped (not supported) | The extension has no standard update server, its update site is disabled, or the update was no longer available when its turn came. | Update it by hand, or enable its update site. |
| 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 below. |
| Already up to date | Shown in the run panel when an extension needed no update any more when its turn came. | Nothing. |
The same skip is not recorded again on every run, so Activity stays readable.
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.
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.