HEART data.integrity-failed H-10005
Data integrity check failed. Data has been changed or damaged when it should not have been.
| Code | HEART data.integrity-failed; inside a message "code": "data.integrity-failed" |
|---|---|
| H-number | H-10005: area 10, code 005 |
| Area | data: Data quality, sync, backups |
| Typical severity | error. A product may set another for its own case. |
| Applies to | Every product that stores data |
Likely causes
- Damaged storage changed the data.
- A software bug wrote over it.
- Someone changed it without permission.
- A file only partly written after a power cut.
How to fix or prevent it
- Stop using the damaged data.
- Restore it from a good backup.
- Check the storage for errors.
- Find out how it changed: look at the access records around that time.
What the HEART does by itself
It raises an error alert and stops trusting that data. Where tampering is possible, it raises a security code as well.
When to call service
If the data matters for safety, money or other people, or tampering is possible.
Related codes
storage.corruptedH-04005: Storage corruptedsecurity.tamper-detectedH-11005: Tampering detecteddata.invalidH-10001: Data invalid
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)