Disconnected Machines No Longer Show As Online Forever
A machine that lost its connection and never properly checked in again could stay marked online indefinitely; it now gets marked offline like any other.
Summary
The desktop app and CLI check in periodically to confirm a machine is still connected. A machine that never completed that first check-in at all — rather than one that simply went quiet after connecting — was being skipped by the process that marks disconnected machines offline, so it could stay listed as "online" indefinitely. It's now treated the same as any other disconnected machine.
What You Gain
Before this fix, most disconnected machines were correctly marked offline a few minutes after they stopped checking in — but a machine that had never successfully checked in even once fell through a gap in that process and could sit listed as online with no end in sight. That's misleading when you're deciding where to send work, or trying to understand whether a machine is actually available to pick up a task.
Now every machine is held to the same standard: if it hasn't checked in recently, including a machine that never checked in at all, it's marked offline so your list of available machines reflects reality.
How It Works
- Machines that never checked in are now treated the same as ones that went quiet — both are marked offline once they're overdue.
- This runs automatically as part of the regular check that keeps machine status up to date; there's nothing to configure.
- A one-off cleanup pass also corrected any machines left incorrectly marked online from before this fix.
Where to Find It
Machine status is shown wherever you view your connected runtimes; it now updates reliably with no action needed from you.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.