# Command: `cronmanager:check-heartbeats`

**Description**: Alert on fleet servers whose CronManager heartbeat is stale
**Status**: completed
**Started**: 2026-09-30 04:15:02 | **Ended**: 2026-09-30 04:15:02 | **Duration**: 0s
**Jobs**: 0 dispatched / 0 completed / 0 failed

---

## Command Output

04:15:02 [INFO] Lock acquired for command: cronmanager:check-heartbeats

04:15:02 [INFO] 🔍 Checking CronManager heartbeats (stale after 36h)

04:15:02 [INFO] ⏭️ kamaterajc — unresolved alert already active, message refreshed

04:15:02 [INFO] ⏭️ ns3018201 — unresolved alert already active, message refreshed

04:15:02 [INFO] ⏭️ ns3022760 — unresolved alert already active, message refreshed

04:15:02 [INFO] 🔍 Unmatched hostnames (no RunCloud server mapping):

04:15:02 [INFO] • ns3018201

04:15:02 [INFO] • ns3022760

04:15:02 [INFO] 🗑️ Purged decommissioned heartbeat: kamaterajc (KamateraJC, last report 355h ago)

04:15:02 [INFO] 📊 Heartbeat check summary:

04:15:02 [INFO] Stale heartbeats: 3

04:15:02 [INFO] Alerts created: 0

04:15:02 [INFO] Decommissioned heartbeats purged: 1

04:15:02 [INFO] Orphaned alerts resolved: 0

04:15:02 [INFO] Lock released for cronmanager:check-heartbeats

---

## Jobs (0)

*No jobs dispatched*

*Exported at 2026-10-03T12:55:10+00:00*