HEART data.out-of-sync H-10003
Data out of sync. Two copies of the same data disagree.
| Code | HEART data.out-of-sync; inside a message "code": "data.out-of-sync" |
|---|---|
| H-number | H-10003: area 10, code 003 |
| Area | data: Data quality, sync, backups |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Products that keep copies of data in more than one place: an app and its cloud, a gateway and its devices |
Likely causes
- A sync stopped halfway, after a lost link or a restart.
- The same data was changed in two places at once.
- Clocks that disagree, so the newer copy looks older.
- A sync job switched off or failing for some time.
How to fix or prevent it
- Read the alert: it names the two copies and how they differ.
- Decide which copy is right, and sync from it.
- Check both clocks.
- Check that the sync job runs, and look at its last result.
What the HEART does by itself
It raises a warning. It does not overwrite either copy by itself when it cannot tell which is right. It resolves when the copies agree.
When to call service
If the copies cannot be brought together, or the data is shared with other people or systems.
Related codes
data.integrity-failedH-10005: Data integrity check failedconnectivity.clock-unsyncedH-03004: Clock not synchroniseddata.missingH-10002: Data missing
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)