api error

[ramarro123]

this is more a "feeling" rather than a bug report...

when a user is "close" to reach 'limit' i got an api errr on claude code. then claude code do a couple of retry and it start again (it's not related to my other issue, that blocked the usage yesterday, this is more intermittend even if look similar)

it's not possible to force an immediate retry on a different account when a limit is reached? or tune the usage of a account to reach 95% instead of 99% so maybe we get some grace calls?

thanks!

[askalf]

What happens today, from the code rather than from memory:

• A new conversation goes to the seat with the most headroom (--pool-strategy=headroom, the default).
• A conversation already bound to a seat stays on it — that is what keeps Claude's prompt cache warm — until the seat's headroom is at or below 2%, or the seat answers a 429 mid-request, at which point the request is retried on the next-best seat before anything reaches the client.

So the retry-on-another-seat you asked for exists, but only at the 429. The gap is the stretch between "nearly spent" and "rejected", where a bound session keeps riding the seat. #1335 makes that line yours: --pool-headroom-floor=5% (env DARIO_POOL_HEADROOM_FLOOR, config pool.headroomFloor) rebinds a session off a seat once its headroom is at or below the floor and keeps new conversations off it — the 95% you asked for.

One thing I cannot tell from here: whether the errors Claude Code shows you are 429s (a window) or 529s (Anthropic overloaded). dario fails over on the first; the second is upstream-wide and no seat helps. If you can paste one of the error bodies, I can say which you are seeing.

[askalf]

Shipped in v6.8.9: --pool-headroom-floor (also DARIO_POOL_HEADROOM_FLOOR or pool.headroomFloor in the config file). It sets the headroom at or below which a seat counts as drained, as a ratio (0.05) or a percent (5%), default 2%, max 50%. A sticky conversation rebinds off a seat at or below the floor and new conversations skip it, so a seat that starts answering API errors in its last few percent can be left alone at, say, 95% instead of ridden into the 429. Default behaviour is unchanged, so nothing moves unless you set it. If you try it, dario status will show which seat is being skipped and why.

[askalf]

Checking back on this. --pool-headroom-floor shipped in v6.8.9, and since v6.10.1 a 429 on one model family no longer parks the whole seat; the current release is 6.12.6.

Did setting the floor (for example 5%) stop the errors near the limit? If they still happen, please paste one error body from Claude Code, or the matching line from dario's log. A 429 is something dario can route around; a 529 overloaded_error comes from Anthropic for every seat at once, so no pool setting avoids it.

Leaving this open until we hear back.

[ramarro123]

I Will check on Monday and give you feedback on that matter

Thank you

[ramarro123]

Today no error when around 95% of usage I did set pool-headroom-floor to 95its that right?

[askalf]

Close, but the floor counts the share that is left on a seat, not the share used. To move off a seat at 95% used, set it to 5%:

--pool-headroom-floor=5%
DARIO_POOL_HEADROOM_FLOOR=5%
"pool": { "headroomFloor": 0.05 }

95 would mean 95% left, which is above the 50% maximum, so dario does not use it. As a flag, dario refuses to start (Invalid --pool-headroom-floor "95"). In the environment or the config file it is ignored and the 2% default stays in place, so if dario started normally today it ran with the default floor.

dario doctor shows the floor it reads from the environment or config file on its Pool routing line; with 5% set, that line includes 5% floor.

Thanks for testing it. If the errors come back near the limit with 5% set, paste one error body and we can tell a 429 (dario routes around it) from a 529 (Anthropic-wide).

[ramarro123]

i can say it work for me, i haven't see any error in the past 3d 👍

[askalf]

Thanks for confirming, and for testing it across three days. Closing this one. If errors come back near the limit with the 5% floor set, reopen it with one error body and we can tell a 429 from a 529.