Merge pull request #3797 from LvckyAPI/fix-incorrect-status

Fix monitoring status stuck
This commit is contained in:
Alexander Holliday authored and GitHub committed 2026-07-30 09:44:15 -07:00
commit ff28e74aca
2 files changed
+45 -3

No files matched your search

+6 -3
View File
@@ -1,7 +1,7 @@
import { IMonitorStatsRepository } from "@/domain/monitor-stats/monitor-stats.repository.interface.js";
import { IMonitorsRepository } from "@/domain/monitors/monitor.repository.interface.js";
import type { Check, CheckDiskInfo, CheckSnapshot } from "@/domain/checks/check.type.js";
import type { Monitor, MonitorStatus } from "@/domain/monitors/monitor.type.js";
import { MonitorStatuses, type Monitor, type MonitorStatus } from "@/domain/monitors/monitor.type.js";
import type {
DockerStatusPayload,
GameStatusPayload,
@@ -218,10 +218,13 @@ export class StatusService implements IStatusService {
const patch: Partial<Monitor> = {};
// 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 isUnknownStatus = !MonitorStatuses.includes(monitor.status);
let newStatus: MonitorStatus = monitor.status;
let statusChanged = false;
if (monitor.status === "initializing" || monitor.status === "maintenance") {
newStatus = status === true ? "up" : "down";
if (monitor.status === "initializing" || monitor.status === "maintenance" || isUnknownStatus) {
newStatus = status ? "up" : "down";
patch.status = newStatus;
statusChanged = newStatus === "down";
}