HEART performance.backlog H-05003
Backlog growing. A queue of waiting work keeps growing.
| Code | HEART performance.backlog; inside a message "code": "performance.backlog" |
|---|---|
| H-number | H-05003: area 05, code 003 |
| Area | performance: Speed, load, heat |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Servers, apps, gateways and devices that queue data |
Likely causes
- Work arrives faster than it is handled.
- A worker or consumer is stuck, so its queue grows.
- An outside service it hands work to is down.
- Messages waiting to be sent while a link is down.
How to fix or prevent it
- Find which queue grows, and what should be emptying it.
- Restart a stuck worker, or add workers.
- Fix the outside service or link, then let the queue drain.
What the HEART does by itself
It raises a warning when the queue passes the product's limit, such as 500 waiting requests. A Playbook may restart a stuck worker. It resolves when the queue is back under the limit.
When to call service
If the queue keeps growing with workers running and services up.
Related codes
performance.overloadedH-05002: Overloadedconnectivity.dependency-unreachableH-03003: A service it relies on cannot be reachedsoftware.crashedH-06002: Crashed
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)