| Previous | Next |
| E_BLUETOOTH_ATT_UNSUPPORTED_GROUP_TYPE | E_BLUETOOTH_ATT_UNKNOWN_ERROR |
E_BLUETOOTH_ATT_INSUFFICIENT_RESOURCES
The resource shortage is reported by the ATT server
E_BLUETOOTH_ATT_INSUFFICIENT_RESOURCES carries ATT error 0x11. Unlike Prepare Queue Full, it is not limited to reliable-write staging. A peripheral can return it when dynamic allocation fails, an application work queue is saturated, a response cannot be constructed, or a hardware-dependent operation cannot reserve what it needs.
The HRESULT does not identify which resource was exhausted. Client-side memory cleanup may be irrelevant because the rejecting endpoint is usually the remote server. A bounded retry can be appropriate only when the peripheral documents the condition as temporary.
Find the constrained server subsystem
- Correlate the error with concurrent connections, notifications, queued writes, and long operations.
- Inspect peripheral heap, buffer-pool, work-queue, and application resource metrics.
- Reduce request concurrency before reducing payload correctness or security requirements.
- Apply backoff and a retry limit so resource pressure is not amplified.
References
- Bluetooth Core: Insufficient Resources
- Zephyr: GATT server callbacks and resource errors
- Apple Core Bluetooth: insufficientResources
Looking for a different code? Search another status or error code.