/ errors · HTTP 507
adapter_unavailable
LoRA adapter cannot fit into memory even when loaded alone.
What it means
A LoRA adapter cannot fit even when loaded alone.
How to recognise it
The gateway answers HTTP 507 with x-ace-error: adapter_unavailable on the response, and a body in the shared error envelope:
{
"error": {
"message": "...",
"type": "adapter_unavailable",
"code": 507
}
}
On a vendor-shaped surface (/anthropic/…, /gemini/…, /bedrock/…) the body wears that vendor's error envelope instead; the x-ace-error header is the same everywhere.
Is it ACE or the provider?
x-ace-error is present only on errors ACE originated. A vendor error relayed from upstream — a real provider 429, a provider 401 for a bad pass-through key — carries no x-ace-error, and its own type and code mean what the provider says. Read the header before deciding whether to retry, re-mint a key or surface the error.
Related
- Error contracts & status codes: the full taxonomy
- Response header specification
- Echo mode: reproduce a call without spending