Kelvin marks a record stale when it was last saved before its system's last save. It is a date comparison and nothing more: Kelvin doesn't look at what changed, so even a save of the system that changed nothing makes older records stale.
- 1
On Reports, find the row whose Status reads Stale. Its basis gives both dates: when the record was saved, and the system's last save.
- 2
Choose the station's name in the ledger to open that station with the same record.
- 3
Check the record against the system as it is now: recalculate it there if the system's figures have moved.
- 4
Save the record again on that station.
- 5
Back on Reports, the row reads Current.
What is judged
Pipe Layout, Equipment, Refrigerant Charge, Energy and BOM & Running Cost records are judged, because each is built from the system's results. Heat Load rooms feed the system rather than read from it, and the Cycle report is the system itself, so neither is judged.
On an HVAC or hydronic project the rule reaches further: a record is stale when it was saved before the last save of anything it is calculated from. A space is judged against the project, an air system against the project and the spaces it serves, a duct network against its air system, and a fan against both. On the water side, pipework is judged against its circuit, and pumps and the vessel against their pipework.
Issuing a stale record anyway
A stale record can still be viewed, downloaded and bundled. The ledger flags it, the foot counts how many stale records are in the bundle, and the event margin names them, so it is never issued without you knowing. An HVAC or hydronic document also names it in its own engineering checks.
Note
Saving a design in Cycle makes every record built from it stale, even when only its name changed. Re-save the downstream records once the design is settled, rather than after every change.