You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the feature you'd like
It would be great if there were a fallback mechanism in case the OpenAI API is unavailable. For example, it could switch to using Anthropic's Claude Sonnet. This would ensure redundancy and make Flowise much more user-friendly by maintaining functionality seamlessly.
The text was updated successfully, but these errors were encountered:
Thanks for the response! I understand the drag-and-drop limitations, but would it be possible to implement a fallback based on HTTP status codes? For example, if the OpenAI API returns a 503, the workflow could try Anthropic's Claude Sonnet.
If that’s not feasible, are there any workarounds you’d recommend for this use case?
Describe the feature you'd like
It would be great if there were a fallback mechanism in case the OpenAI API is unavailable. For example, it could switch to using Anthropic's Claude Sonnet. This would ensure redundancy and make Flowise much more user-friendly by maintaining functionality seamlessly.
The text was updated successfully, but these errors were encountered: