Background health checks now feed deployment health state into the router candidate-filtering pipeline. Unhealthy deployments are excluded proactively instead of waiting for request failures to trigger cooldown. Gated by `enable_health_check_routing: true` in general_settings. Off by default — zero behavior change for existing users. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| pre_call_checks | ||
| router_callbacks | ||
| add_retry_fallback_headers.py | ||
| batch_utils.py | ||
| client_initalization_utils.py | ||
| clientside_credential_handler.py | ||
| common_utils.py | ||
| cooldown_cache.py | ||
| cooldown_callbacks.py | ||
| cooldown_handlers.py | ||
| fallback_event_handlers.py | ||
| get_retry_from_policy.py | ||
| handle_error.py | ||
| health_state_cache.py | ||
| pattern_match_deployments.py | ||
| prompt_caching_cache.py | ||
| response_headers.py | ||
| search_api_router.py | ||