From 92d3068be0e964478ec2cb18f41183cf916a490a Mon Sep 17 00:00:00 2001
From: SergeantPanda <chester.cullen@gmail.com>
Date: Sat, 23 May 2026 21:25:44 -0500
Subject: [PATCH] fix: ensure migrations run automatically after restoring
 backups to prevent missing schema issues

---
 CHANGELOG.md                                      | 4 ++++
 apps/backups/tasks.py                             | 3 +++
 frontend/src/components/backups/BackupManager.jsx | 6 +++---
 3 files changed, 10 insertions(+), 3 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 7e998abd..3464dd31 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Fixed
+
+- **Restoring a backup from an older version left the database with missing schema.** The restore task ran `pg_restore` which replaced the entire database (including the `django_migrations` table) but did not run migrations afterward. If the backup predated a schema migration, the restored database was missing tables and columns added by those migrations, causing 500 errors on every API call. `migrate --noinput` now runs automatically after every restore. The success notification also now recommends a restart to clear stale service state.
+
 ## [0.25.1] - 2026-05-23
 
 ### Fixed
diff --git a/apps/backups/tasks.py b/apps/backups/tasks.py
index f531fef8..a169b7db 100644
--- a/apps/backups/tasks.py
+++ b/apps/backups/tasks.py
@@ -1,6 +1,7 @@
 import logging
 import traceback
 from celery import shared_task
+from django.core.management import call_command
 
 from . import services
 
@@ -61,6 +62,8 @@ def restore_backup_task(self, filename: str):
         backup_file = backup_dir / filename
         logger.info(f"[RESTORE] Backup file path: {backup_file}")
         services.restore_backup(backup_file)
+        logger.info(f"[RESTORE] Running migrations after restore...")
+        call_command('migrate', '--noinput', verbosity=1)
         logger.info(f"[RESTORE] Task {self.request.id} completed successfully")
         return {
             "status": "completed",
diff --git a/frontend/src/components/backups/BackupManager.jsx b/frontend/src/components/backups/BackupManager.jsx
index 02b7d15d..c58755b2 100644
--- a/frontend/src/components/backups/BackupManager.jsx
+++ b/frontend/src/components/backups/BackupManager.jsx
@@ -439,12 +439,12 @@ export default function BackupManager() {
     try {
       await API.restoreBackup(selectedBackup.name);
       notifications.show({
-        title: 'Success',
+        title: 'Restore Complete',
         message:
-          'Backup restored successfully. You may need to refresh the page.',
+          'Backup restored successfully. A restart is recommended to ensure all services are running against the restored data.',
         color: 'green',
       });
-      setTimeout(() => window.location.reload(), 2000);
+      setTimeout(() => window.location.reload(), 4000);
     } catch (error) {
       notifications.show({
         title: 'Error',