From b2d6e1bcfd77c4ea058067a6e4a1c4008ff08152 Mon Sep 17 00:00:00 2001
From: Gmer4Lfe <gmer4lfe@gmail.com>
Date: Tue, 21 Jul 2026 16:50:38 -0400
Subject: [PATCH] Fix Emby/critical-data never restarting in weekly sync window
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

stop_local_containers() reads LOCAL_CRITICAL_CONTAINER_NAMES, which was
never set here — only rsync.sh sets it, in a child process that can't
propagate back. Local stop always no-op'd, so the rebuild-on-new-image
step never had anything to act on.
---
 Orchestrators/weekly_sync_maintenance.sh | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/Orchestrators/weekly_sync_maintenance.sh b/Orchestrators/weekly_sync_maintenance.sh
index 726a7ba..4783657 100755
--- a/Orchestrators/weekly_sync_maintenance.sh
+++ b/Orchestrators/weekly_sync_maintenance.sh
@@ -185,6 +185,8 @@ else
     # Load container lists for stop functions
     read -r -a CRITICAL_CONTAINER_NAMES <<< \
         "${PROFILE_CRITICAL_CONTAINER_NAMES[critical-data]:-} ${PROFILE_CRITICAL_CONTAINER_NAMES[emby]:-}"
+    read -r -a LOCAL_CRITICAL_CONTAINER_NAMES <<< \
+        "${PROFILE_CRITICAL_CONTAINER_NAMES[critical-data]:-} ${PROFILE_CRITICAL_CONTAINER_NAMES[emby]:-}"
     read -r -a DELAYED_CONTAINERS       <<< "${PROFILE_DELAYED_CONTAINERS[critical-data]:-}"
     CONTAINER_DELAY="${PROFILE_CONTAINER_DELAY[critical-data]:-15}"