Staleness
How Scanopy flags hosts, services, and subnets that discovery hasn't seen recently.
Scanopy marks an entity Stale when discovery hasn't observed it within its network's staleness window — a device powered off, a container removed, a host that moved. Nothing is deleted.
Stale does not mean gone. A stale host might be switched off, on the road, or briefly unreachable during a scan. Scanopy reports only how long it's been since discovery last saw it.
The staleness window
Each network has its own window, because staleness is only meaningful relative to how often that network is scanned — a segment swept every 15 minutes and one swept monthly need very different thresholds.
The default is 28 days. Set a network's own in the network edit modal (Assets > Networks → select the network → Consider entities stale after), as days and hours; leave it blank for the default. Set it comfortably above the network's scan interval so a normal gap between scans never trips it.
See Networks for where this fits among a network's settings.
What can go stale
Only what discovery manages: hosts, services, and subnets it found and keeps re-observing. Anything you created by hand never goes stale, since there's no scan timestamp to judge it against.
Every entity is judged on its own last-seen time, independently of its parent. A service on a host that's gone quiet is stale only if that service hasn't been seen within the window — a recently observed service on an otherwise-dark host reads as current, and vice versa.
Where it shows up
- Lists — hosts, services, and subnets carry a Stale badge past their window, with a Stale only filter and sorting by last-seen.
- Topology — stale nodes carry a Stale tag and a "last seen" detail. A By staleness filter (Current / Stale) fades everything else. See Customizing Views.
The tag is amber rather than red, matching the daemon status convention where red means broken and amber means behind.