HEART system.heart-unwell H-01005

The HEART itself is unwell. The HEART itself has a problem. The product may be fine.

Likely causes

• The HEART cannot save its state: its storage is full or read-only.
• One of its own checks or Playbooks keeps failing.
• Its configuration or signal table is invalid, so it cannot watch everything it should.
• It is short of memory or time on a small processor, so checks run late.
• It cannot read the product's data, for example after a firmware change on the product side.

How to fix or prevent it

1. Read the explanation: it says which part of the HEART is affected.
2. Check the HEART's configuration and signal table against the product's current firmware.
3. Free space or memory for the HEART, or restart it.
4. Update the HEART software to the latest version.

What the HEART does by itself

It reports this about itself, while the product goes on doing its job. It keeps watching what it still can, and tells a person. It does not act on the product while it is unwell.

When to call service

If it does not clear after a restart and an update. The product may still work, but it is not being watched properly.

Related codes

• system.flatline H-01003: No Pulse (flatline)
• software.config-invalid H-06005: Settings invalid
• storage.write-failed H-04003: Write failed
• performance.memory-exhausted H-05004: Memory exhausted

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)