HEART connectivity.dependency-unreachable H-03003
A service it relies on cannot be reached. An outside service or system it relies on cannot be reached.
| Code | HEART connectivity.dependency-unreachable; inside a message "code": "connectivity.dependency-unreachable" |
|---|---|
| H-number | H-03003: area 03, code 003 |
| Area | connectivity: Network and links to other systems |
| Typical severity | error. A product may set another for its own case. |
| Applies to | Servers and apps that use outside services; Gateways in front of controllers or PLCs |
Likely causes
- An outside service is down: a payment provider, a cloud API, a backend.
- A controller the HEART reads from stopped answering, such as a PLC behind a gateway or a charger's main controller.
- Wrong address, or credentials that expired.
- A firewall rule or network change blocks the way.
How to fix or prevent it
- Read the alert: it names the service or part that does not answer.
- Check that service's own status page, or the controller's power and cable.
- Check addresses, keys and certificates in the settings.
- Check firewall and network changes made recently.
- To prevent it: a second provider where possible, and timeouts that fail safely.
What the HEART does by itself
It raises an error alert, often after several failed tries (component.failed events) in a short time. A Playbook may retry or switch to a second provider if the product has one. It resolves when the service answers again (component.recovered).
When to call service
If the service is one you run yourself, or the controller stays silent with power and cable in order.
Related codes
connectivity.link-lostH-03001: Network link lostai.provider-unavailableH-07001: AI provider unavailableperformance.backlogH-05003: Backlog growing
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)