HEART system.flatline H-01003
No Pulse (flatline). No Pulse for three intervals. Raised by whoever is watching, not by the system itself.
| Code | HEART system.flatline; inside a message "code": "system.flatline" |
|---|---|
| H-number | H-01003: area 01, code 003 |
| Area | system: The whole system |
| Typical severity | error. A product may set another for its own case. |
| Applies to | Anything watched by a Gateway, a Command Center or HEART Hub |
Likely causes
- The product is switched off, or has lost power with no backup.
- Its network link is down, so its Pulse cannot get out (the product itself may be fine).
- Its HEART has crashed or hung, while the product goes on working.
- The product is asleep longer than it said it would be, or did not say it sleeps at all.
- A firewall, router or Gateway between the product and its watcher blocks its reports.
How to fix or prevent it
- Check that the product has power and is switched on.
- Check its network: Wi-Fi, cable, mobile signal, or the Gateway it reports through.
- Look at the product itself: if it still works, its HEART or its link is the problem, not the product.
- Restart the HEART, or the product if that is safe.
- For battery products that sleep: make sure each report says how long it will sleep, so a sleep is not mistaken for a flatline.
What the HEART does by itself
A system never raises this about itself: it cannot. Whoever watches it, such as a Gateway or HEART Hub, raises it after three Pulse intervals with no Pulse, sets the status to unknown, and tells the owner (HEART Hub sends one email). It resolves by itself with the next Pulse.
When to call service
If the product has power and network but stays silent after a restart, or if it is a product that must never be unwatched, such as a medical transmitter or a pump station.
Related codes
connectivity.link-lostH-03001: Network link lostpower.supply-lostH-02001: Main power lostsystem.heart-unwellH-01005: The HEART itself is unwellsystem.unexpected-restartH-01004: Unexpected restart
Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written
HEART storage.full. Things that simply happen, such as system.started, are event types, not faults.
The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7.
All of it, as data: fault-codes.json.
All fault codes, by area · All fault codes, by H-number · Problem types (API errors)