Troubleshooting

Nothing is updated automatically.

1. Open Overview. A red banner or an orange health pill tells you what is missing. See Making sure scheduled updates run.
2. Is Auto-update on for the extension? Check the switch on the Extensions screen.
3. Open Dry run. The Reason column tells you why each update would or would not be installed.
4. On a site with few visitors, tasks start late. Set up Web Cron or a command line cron job.

Updates are installed, but much later than planned. The Lazy Scheduler only starts a task when somebody visits the site. See The Lazy Scheduler needs visitors and Setting up Web Cron.

Updates wait although the maintenance window was open. No run started inside the window, because nobody visited the site during those hours. Set up a cron job as described in Setting up Web Cron.

"Automatic updates are not running" on the Overview. Follow the Fix line of each listed problem, then click Check again.

An extension always shows "Download refused (licence)". Its download key is missing or has expired. Enter it under System → Update Sites.

An extension always shows "Checksum mismatch". The developer's update server publishes a checksum that does not match the package. AutoPilot refuses such packages on purpose. Tell the developer.

"Verification failed", but the site looks fine. Read the message. If it names an HTTP status such as 401 or 503, the site could not load its own pages: it may be offline, password-protected, or blocking requests from its own server. If the site works, click Dismiss on the Overview, and consider turning off the two page checks under Settings → Verification checks.

"Snapshot failed". The update was not installed. Check that the snapshot folder is writable and that there is enough disk space. For very large tables, lower Rows per Chunk, or exclude log tables under Tables Not Snapshotted.

A manual run stopped half way. The browser tab was closed or left AutoPilot. Open AutoPilot again and the run continues. If the health check shows a stopped run, click Release lock and start the remaining updates again.

The Approvals screen is empty, but I expected an update there. A request appears only when approval is required for that extension and a scheduled run has looked at it. Check the extension's Effective settings and the Dry run.

No emails arrive. Check Settings → Notifications. Check that the Super Users have Receive System Emails set to Yes. Send a test mail from System → Global Configuration → Server → Send Test Mail. Logs show a line for every email that was sent.

Emails arrive in English although the pack is installed. The email uses each Super User's own backend language. Set it in the user's profile, under Basic Settings → Backend Language.

I lost the recovery key. Create a new one under Settings → Emergency recovery. The old one stops working. If the administrator does not load either, see If something does not go as planned.

I need more detail. Turn on Settings → Advanced → Debug Logging, repeat the action, and read the run in Logs. Turn debug logging off afterwards.