HEART data.invalid H-10001
Data invalid. Data fails its checks.
| Code | HEART data.invalid; inside a message "code": "data.invalid" |
|---|---|
| H-number | H-10001: area 10, code 001 |
| Area | data: Data quality, sync, backups |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Every product that receives data from sensors, devices or other systems |
Likely causes
- A device or client sends data in the wrong shape, such as a missing field or text where a number belongs.
- One side was updated and changed its format, and the other was not.
- Wrong units, such as Fahrenheit sent where Celsius is expected.
- Data damaged on a poor link, so a checksum fails.
- A value outside the range the product accepts.
How to fix or prevent it
- Read the alert: it names the data that failed and the check it failed.
- Check the versions of the sender and the receiver, and update the older one.
- Check units and scales in the sender's settings.
- Fix the sender, or ask its maker to, if it keeps sending bad data.
What the HEART does by itself
It refuses data that fails its checks, so bad values are not acted on, and records why. It raises a warning when it keeps happening. It resolves when good data flows again.
When to call service
If the sender is a part you cannot change, or bad data reaches decisions that matter.
Related codes
software.version-mismatchH-06006: Version mismatchdata.integrity-failedH-10005: Data integrity check faileddata.missingH-10002: Data missingsensors.out-of-rangeH-08002: Reading out of range
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)