docs: remove enable_pre_call_checks requirement from order docs

Order-based routing and fallback work without enable_pre_call_checks
in the current code. Remove the stale requirement from both doc files.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Sameer Kankute 2026-03-26 12:43:11 +05:30
parent 2950677e5d
commit 158732db59
No known key found for this signature in database
2 changed files with 1 additions and 16 deletions

View file

@ -325,15 +325,8 @@ model_list:
model: azure/gpt-4-fallback
api_key: os.environ/AZURE_API_KEY_2
order: 2 # 👈 Used when order=1 fails
router_settings:
enable_pre_call_checks: true # 👈 Required for 'order' to work
```
:::important
The `order` parameter requires `enable_pre_call_checks: true` in `router_settings`.
:::
### How order-based fallback works
When a request to an `order=1` deployment fails (connection error, 404, 429, etc.), the router automatically tries `order=2` deployments, then `order=3`, and so on. Each order level gets its own set of retries before escalating to the next.
@ -360,7 +353,6 @@ model_list:
api_key: os.environ/OPENAI_API_KEY
router_settings:
enable_pre_call_checks: true
fallbacks:
- gpt-4:
- gpt-4-fallback # tried after all order levels fail

View file

@ -869,13 +869,9 @@ model_list = [
},
]
router = Router(model_list=model_list, enable_pre_call_checks=True) # 👈 Required for 'order' to work
router = Router(model_list=model_list)
```
:::important
The `order` parameter requires `enable_pre_call_checks=True` to be set on the Router.
:::
</TabItem>
<TabItem value="proxy" label="PROXY">
@ -892,9 +888,6 @@ model_list:
model: azure/gpt-4-fallback
api_key: os.environ/AZURE_API_KEY_2
order: 2 # 👈 Tried when order=1 fails
router_settings:
enable_pre_call_checks: true # 👈 Required for 'order' to work
```
</TabItem>