Recover from a failed update
Purpose
Section titled “Purpose”Return the framework to a known-good runtime while preserving evidence and database backups.
Audience
Section titled “Audience”Framework administrators and deployment operators.
Prerequisites
Section titled “Prerequisites”Access to application logs, the previous framework version, and the latest verified backup.
Procedure
Section titled “Procedure”- Record the update job error and backup path from System Maintenance.
- Check available disk space and application/updater logs.
- Windows: inspect the timestamped framework backup and run
Update.cmdafter correcting the cause. - Docker: verify whether the sidecar restored the previous container, then follow the manual rollback procedure.
- Start the previous framework version and verify data before retrying.
- Restore the
.emubackuponly if data verification fails or release notes explicitly require database rollback. - Restore
.emu-secret.keyor the configuredEMU_SECRET_KEY_PATHseparately. After returning to a version that supports SMTP, verify the connection and send a test message.
Do not mix framework files from multiple releases. Preserve the failed state until logs and backups have been collected.