From bb6ea3b23c464d50d6277dceb2a23183a875ebc0 Mon Sep 17 00:00:00 2001 From: rcourtman Date: Mon, 10 Nov 2025 20:32:04 +0000 Subject: [PATCH] Fix offline alert state not displaying in thresholds UI (related to #683) When disabling offline alerts for VMs/containers, the setting was being persisted correctly and honored by the alert system, but the UI always showed "Warn" instead of the actual saved state. Root cause: When reconstructing the overrides list from backend config, the guest override mapping was copying poweredOffSeverity but omitting disableConnectivity, causing ResourceTable to fall back to global defaults. Fix: Add disableConnectivity field to guest override reconstruction in Alerts.tsx (line 676), matching the pattern already used for Docker containers. --- frontend-modern/src/pages/Alerts.tsx | 1 + 1 file changed, 1 insertion(+) diff --git a/frontend-modern/src/pages/Alerts.tsx b/frontend-modern/src/pages/Alerts.tsx index c8671c2..60517cc 100644 --- a/frontend-modern/src/pages/Alerts.tsx +++ b/frontend-modern/src/pages/Alerts.tsx @@ -673,6 +673,7 @@ const [appriseConfig, setAppriseConfig] = createSignal( node: guest.node, instance: guest.instance, disabled: thresholds.disabled || false, + disableConnectivity: thresholds.disableConnectivity || false, poweredOffSeverity: thresholds.poweredOffSeverity === 'critical' ? 'critical'