From 3201653f199aaf27ac036e4bf47fafa011ec3569 Mon Sep 17 00:00:00 2001 From: Iven Schlenther Date: Mon, 27 Jul 2026 15:02:37 +0200 Subject: [PATCH] Fix monitor status handling: replace `isKnownStatus` with `isUnknownStatus` for clarity and simplify initialization logic. --- server/src/service/statusService.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/server/src/service/statusService.ts b/server/src/service/statusService.ts index db83de08f..773a49e27 100755 --- a/server/src/service/statusService.ts +++ b/server/src/service/statusService.ts @@ -220,11 +220,11 @@ export class StatusService implements IStatusService { // Resolve "initializing" and "maintenance" up front, incidents should be created on initialization && down // Unknown values (e.g. legacy boolean statuses from old versions) are resolved the same way, // otherwise computeReachability can never transition them and they stay stuck forever. - const isKnownStatus = (MonitorStatuses as readonly string[]).includes(monitor.status); + const isUnknownStatus = !MonitorStatuses.includes(monitor.status); let newStatus: MonitorStatus = monitor.status; let statusChanged = false; - if (monitor.status === "initializing" || monitor.status === "maintenance" || !isKnownStatus) { - newStatus = status === true ? "up" : "down"; + if (monitor.status === "initializing" || monitor.status === "maintenance" || isUnknownStatus) { + newStatus = status ? "up" : "down"; patch.status = newStatus; statusChanged = newStatus === "down"; }