Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Fallback when OpenAI API (Or any other API) is not available #3774

Closed
kforstner opened this issue Dec 27, 2024 · 2 comments
Closed

Comments

@kforstner
Copy link

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.

@HenryHengZJ
Copy link
Contributor

Due to the drag and drop interface, i dont think we can achieve something like that, maybe in the future!

@kforstner
Copy link
Author

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants