Automatic API Fallback & Recovery
Choose when an alternative may be used.
Configure whether an alternative available route may take over after a confirmed restriction.
Choose when an alternative may be used.
When you want controlled continuation during outages or provider limits.
A temporary provider problem should not silently create unexpected paid usage. Fallback settings describe which alternatives may be considered and under what constraints.
Keep fallback disabled for subscription-only work, or allow a configured alternative with limits. Unknown usage information alone is not permission for a paid run.
How to get started.
From your first choice to the result. Here is how to use this feature in your own project.
- 01
Explicitly enable or disable fallback and choose allowed routes and preferences.
- 02
Linqbase evaluates the reported error or restriction and current availability.
- 03
Review which route the conversation actually uses and inspect a paused task before continuing.
How it could work for you.
Permit an API fallback for an urgent task while keeping routine conversations on the subscription route.
How to assess the result
The alternative needs its own access and budget. Provider availability can still prevent continuation.
Where to find it.
Settings → AI → Fallback
Available actions depend on your plan, mode and project state. Features that require a task become available within an appropriate conversation.What is saved?
Fallback preferences and route changes are recorded.
What you need to know
Missing limit data is not permission to start paid API execution. Another route can have different costs and capabilities.