HEART data.missing H-10002
Data missing. Expected data has not arrived.
| Code | HEART data.missing; inside a message "code": "data.missing" |
|---|---|
| H-number | H-10002: area 10, code 002 |
| Area | data: Data quality, sync, backups |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Every product that expects data from sensors, devices or other systems |
Likely causes
- A source has stopped sending: a sensor, a device in the field, an upstream system.
- The link between them is down.
- A scheduled job that should produce the data did not run.
- The source is asleep longer than expected, or its battery is flat.
How to fix or prevent it
- Read the alert: it names what is missing, and since when.
- Check the source: power, battery, and its own alerts.
- Check the link between the source and the product.
- Check that scheduled jobs ran, and run a missed one by hand.
What the HEART does by itself
It raises a warning when expected data is late, and never fills the gap with invented values. It may mark results that depend on the missing data as uncertain. It resolves when the data arrives.
When to call service
If the source works and the link is up, but the data still does not arrive.
Related codes
sensors.no-readingH-08001: No readingconnectivity.link-lostH-03001: Network link lostdata.out-of-syncH-10003: Data out of syncsystem.flatlineH-01003: No Pulse (flatline)
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)