HEART Embedded Systems logoHEART

HEART system.main-function-degraded H-01002

Main function degraded. The main job works, but less well than normal.

CodeHEART system.main-function-degraded; inside a message "code": "system.main-function-degraded"
H-numberH-01002: area 01, code 002
Areasystem: The whole system
Typical severitywarning. A product may set another for its own case.
Applies toEvery product with a HEART

Likely causes

How to fix or prevent it

  1. Read the explanation: it says what is weaker than normal and by how much.
  2. Clean or replace what is fouled: filters, strainers, nozzles, fans, sensors.
  3. Refill or recharge what is low before it runs out.
  4. Check for a second open alert, such as performance.too-hot or sensors.drift: it is often the real cause.
  5. To prevent it: keep to the maintenance schedule, and watch for this warning becoming more frequent.

What the HEART does by itself

It raises a warning alert and sets its status to degraded. A Playbook may take a small step the product allows, such as switching to a standby part or reducing load, within its guards. It tells a person if the condition lasts. The alert resolves by itself when the job is back to normal.

When to call service

If it lasts more than a day, keeps coming back after cleaning, or turns into system.main-function-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)