From f845f02df0a4d6720a1886cc54d2d4af2e08e513 Mon Sep 17 00:00:00 2001 From: Teknium <127238744+teknium1@users.noreply.github.com> Date: Mon, 7 Sep 2026 02:35:42 -0700 Subject: [PATCH] docs: clarify fallback credential and cooldown behavior --- website/docs/user-guide/features/fallback-providers.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/docs/user-guide/features/fallback-providers.md b/website/docs/user-guide/features/fallback-providers.md index bc3adabc63..9fe53c19e1 100644 --- a/website/docs/user-guide/features/fallback-providers.md +++ b/website/docs/user-guide/features/fallback-providers.md @@ -214,6 +214,8 @@ Main provider + main model → auxiliary..fallback_chain → fallback_providers / fallback_model → built-in auxiliary discovery chain ``` +A billing or quota failure quarantines only the failed custom endpoint for the auxiliary health cooldown, not every route registered as `custom`. A healthy local endpoint with a different base URL remains eligible for fallback and subsequent auto routing. Aliases for the same custom endpoint share its health state. Built-in providers retain their shared-account health checks. + The task-specific chain is most precise and wins when present. The top-level `fallback_providers` chain is the same policy the main agent uses, so free-only or same-provider fallback rules apply to auxiliary tasks on `auto` as well. **Built-in text discovery chain (compression, web extract, title generation, etc.):**