An update was interrupted
Read the existing update plan and preserve its recovery material before deciding whether to resume or roll back.
Recognize the symptom
The update command stopped, the web page reports an unfinished plan or maintenance mode remains active. Note the plan identifier and last recorded error. An interrupted update is not a reason to upload another archive or begin an unrelated installation over the same directory.
Possible causes
Execution can stop because of a specific filesystem, database, runtime or package-validation failure. The correct next step depends on the phase reached. A failed preparation and a partially applied update do not have the same recovery requirements; inspect the stored plan rather than guessing.
Check before changing anything
Open Administration → Updates and read the plan status. From the actual application directory, the updater’s --status command provides the current state. Use the PHP executable and command context appropriate to that installation, especially when a non-default PHP binary was selected.
Read updater status
Run from the installed application directory with the installation’s PHP executable.
Commandphp utility/update.php --status
Take a targeted action
Correct the recorded cause and follow the resume or rollback command generated for that exact plan. Keep maintenance markers, plan files and recovery backups intact. Do not edit or replace a frozen release archive, manually delete recovery directories or clear maintenance merely to reopen the UI.
Verify the result
Read status again and confirm the plan reached its documented completed state. Run the relevant diagnostics and verify the application behavior that matters to users. Cleanup is a separate supported operation for concluded plans; removing recovery material also removes the corresponding rollback option.