feat: implement "force fallback" strategy for unavailable providers#130
Open
LinearSakana wants to merge 3 commits intodecolua:masterfrom
Open
feat: implement "force fallback" strategy for unavailable providers#130LinearSakana wants to merge 3 commits intodecolua:masterfrom
LinearSakana wants to merge 3 commits intodecolua:masterfrom
Conversation
added 3 commits
February 15, 2026 22:04
* Add `forceFallback` toggle to Profile page under Routing Strategy * Update auth service to check settings for force fallback configuration * Add `forceFallback` to default database settings
Open
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces a Force Fallback option to improve system resilience against temporary network glitches or endpoint misconfigurations.
Problem
Currently, if all endpoints for a specific provider encounter errors (e.g., due to a temporary network flap or client-side setting errors), the system puts them into cooldown. Users must wait for the cooldown to expire before retrying, even if the underlying issue has been resolved.
Solution
Added a new routing setting that allows the system to automatically pick the endpoint with the minimum remaining cooldown time when all other options are unavailable. This ensures requests can still be attempted instead of failing immediately.
Key Changes
getProviderCredentials
logic to support forced selection of the least-rate-limited endpoint.