HEART connectivity.clock-unsynced H-03004
Clock not synchronised. The clock cannot be checked against a time source.
| Code | HEART connectivity.clock-unsynced; inside a message "code": "connectivity.clock-unsynced" |
|---|---|
| H-number | H-03004: area 03, code 004 |
| Area | connectivity: Network and links to other systems |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Every connected product, especially those using certificates or schedules |
Likely causes
- No network access to a time server (NTP), or NTP blocked by a firewall.
- A flat clock battery, so the clock resets after each power cut.
- A wrong time-server address in the settings.
- A product that has been offline for a long time.
How to fix or prevent it
- Check that the product can reach a time server.
- Replace the clock battery if it has one.
- Set the right time-server address.
- Run sync_time if the product offers it.
What the HEART does by itself
It raises a warning and marks the times it records as uncertain. A Playbook may run sync_time. It resolves once the clock has been checked against a time source. A wrong clock matters: certificates, logs and schedules depend on it.
When to call service
If the clock keeps drifting or resetting after a new battery.
Related codes
security.certificate-expiredH-11004: Certificate expireddata.invalidH-10001: Data invalidconnectivity.link-lostH-03001: Network link lost
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)