Which leads to models list breakdown due 429 or another unsuccessful fetch among spam calls
and this leads to chat page breakdown and need to refresh page.
Desired Solution you'd like
please set a limit for this calls as cache, or let the call turned off, for conditions that models list is constant and user-defined
Alternatives Considered
No response
Additional Context
No response
Originally created by @steveepreston on GitHub (Jul 12, 2025).
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
### Problem Description
Problem explained here: https://github.com/open-webui/open-webui/issues/15662
Which leads to models list breakdown due 429 or another unsuccessful fetch among spam calls
and this leads to chat page breakdown and need to refresh page.
### Desired Solution you'd like
please set a limit for this calls as cache, or let the call turned off, for conditions that models list is constant and user-defined
### Alternatives Considered
_No response_
### Additional Context
_No response_
Model Cache feature already exists in dev, and calling /models multiple times should NOT break the system and this has been already battle tested with deployments over 50k+ users. I'd suggest you check for your reverse proxy configuration.
@tjbck commented on GitHub (Jul 12, 2025):
Model Cache feature already exists in dev, and calling `/models` multiple times should NOT break the system and this has been already battle tested with deployments over 50k+ users. I'd suggest you check for your reverse proxy configuration.
@steveepreston commented on GitHub (Jul 12, 2025):
@tjbck Thanks for note 🙏
Model Cache feature already exists in dev
will dev merged with main for next version?
calling /models multiple times should NOT break the system
agree, but it break in other way: third-party endpoint server rate limit because of calling an api multiple time at once, this leads that one of /models responses is not ok, then open-webui clears the models menu, and page need refresh to load models again after 429 state
@steveepreston commented on GitHub (Jul 12, 2025):
@tjbck Thanks for note 🙏
> Model Cache feature already exists in dev
will `dev` merged with main for next version?
> calling /models multiple times should NOT break the system
agree, but it break in other way: third-party endpoint server rate limit because of calling an api multiple time at once, this leads that one of `/models` responses is not ok, then open-webui clears the models menu, and page need refresh to load models again after 429 state
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @steveepreston on GitHub (Jul 12, 2025).
Check Existing Issues
Problem Description
Problem explained here: https://github.com/open-webui/open-webui/issues/15662
Which leads to models list breakdown due 429 or another unsuccessful fetch among spam calls
and this leads to chat page breakdown and need to refresh page.
Desired Solution you'd like
please set a limit for this calls as cache, or let the call turned off, for conditions that models list is constant and user-defined
Alternatives Considered
No response
Additional Context
No response
@rgaricano commented on GitHub (Jul 12, 2025):
I commented in https://github.com/open-webui/open-webui/issues/15662#issuecomment-3064937168
@tjbck commented on GitHub (Jul 12, 2025):
Model Cache feature already exists in dev, and calling
/modelsmultiple times should NOT break the system and this has been already battle tested with deployments over 50k+ users. I'd suggest you check for your reverse proxy configuration.@steveepreston commented on GitHub (Jul 12, 2025):
@tjbck Thanks for note 🙏
will
devmerged with main for next version?agree, but it break in other way: third-party endpoint server rate limit because of calling an api multiple time at once, this leads that one of
/modelsresponses is not ok, then open-webui clears the models menu, and page need refresh to load models again after 429 state