docs: refresh failover generic error refs

This commit is contained in:
Peter Steinberger
2026-04-04 16:18:07 +01:00
parent 6067fe59d8
commit bcaff8c208
2 changed files with 18 additions and 0 deletions

View File

@@ -129,6 +129,14 @@ validation failures) are treated as failoverworthy and use the same cooldowns
OpenAI-compatible stop-reason errors such as `Unhandled stop reason: error`,
`stop reason: error`, and `reason: error` are classified as timeout/failover
signals.
Provider-scoped generic server text can also land in that timeout bucket when
the source matches a known transient pattern. For example, Anthropic bare
`An unknown error occurred` and JSON `api_error` payloads with transient server
text such as `internal server error`, `unknown error, 520`, `upstream error`,
or `backend error` are treated as failover-worthy timeouts. Generic internal
fallback text such as `LLM request failed with an unknown error.` or a bare
`Provider returned error` stays conservative and does not trigger failover by
itself.
Cooldowns use exponential backoff:

View File

@@ -2454,6 +2454,16 @@ for usage/billing and raise limits as needed.
`input is too long for the model` stay on the compaction/retry path instead
of advancing model fallback.
Generic server-error text is intentionally narrower than "anything with
unknown/error in it". OpenClaw does treat provider-scoped transient shapes
such as Anthropic bare `An unknown error occurred`, stop-reason errors like
`Unhandled stop reason: error`, and JSON `api_error` payloads with
transient server text (`internal server error`, `unknown error, 520`,
`upstream error`, `backend error`) as timeout/failover signals. But generic
internal fallback text like `LLM request failed with an unknown error.` or
a bare `Provider returned error` stays conservative and does not trigger
model fallback by itself.
</Accordion>
<Accordion title='What does "No credentials found for profile anthropic:default" mean?'>