LLM/moltbot
1
0
Fork 0
mirror of https://github.com/moltbot/moltbot.git synced 2026-04-23 14:45:46 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: clarify failover 402 handling

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-04 14:46:32 +01:00
parent 73584b1d33
commit 3bc2e47966
3 changed files with 16 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/help/faq.md
View File

@@ -2367,6 +2367,11 @@ for usage/billing and raise limits as needed.
`ThrottlingException`, `resource exhausted`, and periodic usage-window
limits (`weekly/monthly limit reached`) as failover-worthy rate limits.
Some HTTP `402` responses also stay in that transient bucket. If the
message looks like a retryable usage-window or organization/workspace spend
limit (`daily limit reached, resets tomorrow`, `organization spending limit
exceeded`), OpenClaw treats it as `rate_limit`, not a long billing disable.
Context-overflow errors are different: signatures such as
`request_too_large`, `input exceeds the maximum number of tokens`, or
`input is too long for the model` stay on the compaction/retry path instead