HEART system.undo-failed H-01006
A change could not be undone. A change the HEART made could not be undone, so the system is left changed. A person must look.
| Code | HEART system.undo-failed; inside a message "code": "system.undo-failed" |
|---|---|
| H-number | H-01006: area 01, code 006 |
| Area | system: The whole system |
| Typical severity | critical. A product may set another for its own case. |
| Applies to | Products whose HEART makes changes on its own (Autonomy Level A3 and above) |
Likely causes
- The HEART tried a change as a Trial, and the step that puts things back failed.
- The part it changed stopped answering, so the old setting could not be written back.
- Someone or something else changed the same setting in the meantime.
- The link to the product was lost during the undo.
How to fix or prevent it
- Read the alert: it names the change, the old value and the new one.
- Check the setting on the product, and set it back by hand if it is still changed.
- Find out why the undo failed (a part not answering, a lost link) before allowing that Playbook again.
What the HEART does by itself
It records tending.undo-failed, raises this critical alert, tells a person at once, and makes no further automatic change of the same kind until a person has looked.
When to call service
If you cannot set the value back yourself, or the changed setting matters for safety or for the product's main job.
Related codes
actuators.not-respondingH-09001: Actuator not respondingconnectivity.link-lostH-03001: Network link lostsystem.main-function-degradedH-01002: Main function degraded
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)