Originally created by @Xeroxxx on GitHub (Mar 26, 2025).
Originally assigned to: @tjbck on GitHub.
Check Existing Issues
I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
0.5.20
Ollama Version (if applicable)
0.6.2-cuda
Operating System
Debian (Kubernetes Cluster)
Browser (if applicable)
Edge 136
Confirmation
I have read and followed all instructions in README.md.
I am using the latest version of both Open WebUI and Ollama.
I have included the browser console logs.
I have included the Docker container logs.
I have listed steps to reproduce the bug in detail.
Expected Behavior
When a Filter or Pipeline as Function raised a error message, it will be raised with "raise Exception("Rate limit exceeded. Please try again later.")"
The error message is displayed and should be displayed in the conversation.
Actual Behavior
The message raised will only be displayed once. After reloading/browser restart/relogin the message is non persistent and the conversaiton does not show the error message and keeps showing it loads the message.
Steps to Reproduce
Use any function that can raise an error/exception.
Raise an exception.
Refresh browser/relogging/restart browser
Switch to conversation.
Logs & Screenshots
See above. No error messages or non 200 HTTP Codes in Log.
Additional Information
No response
Originally created by @Xeroxxx on GitHub (Mar 26, 2025).
Originally assigned to: @tjbck on GitHub.
### Check Existing Issues
- [x] I have searched the existing issues and discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
0.5.20
### Ollama Version (if applicable)
0.6.2-cuda
### Operating System
Debian (Kubernetes Cluster)
### Browser (if applicable)
Edge 136
### Confirmation
- [x] I have read and followed all instructions in `README.md`.
- [x] I am using the latest version of **both** Open WebUI and Ollama.
- [x] I have included the browser console logs.
- [x] I have included the Docker container logs.
- [x] I have listed steps to reproduce the bug in detail.
### Expected Behavior
When a Filter or Pipeline as Function raised a error message, it will be raised with "raise Exception("Rate limit exceeded. Please try again later.")"
The error message is displayed and should be displayed in the conversation.

### Actual Behavior
The message raised will only be displayed once. After reloading/browser restart/relogin the message is non persistent and the conversaiton does not show the error message and keeps showing it loads the message.

### Steps to Reproduce
Use any function that can raise an error/exception.
Raise an exception.
Refresh browser/relogging/restart browser
Switch to conversation.
### Logs & Screenshots
See above. No error messages or non 200 HTTP Codes in Log.
### Additional Information
_No response_
GiteaMirror
added the bug label 2025-11-11 15:57:06 -06:00
Did you check with Pipelines as well? I remember just getting "Connection Lost" instead of the exception actual message. Sry forgot about that.
@Xeroxxx commented on GitHub (Mar 28, 2025):
> Addressed in dev!
Thank you!!
Did you check with Pipelines as well? I remember just getting "Connection Lost" instead of the exception actual message. Sry forgot about that.
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 @Xeroxxx on GitHub (Mar 26, 2025).
Originally assigned to: @tjbck on GitHub.
Check Existing Issues
Installation Method
Docker
Open WebUI Version
0.5.20
Ollama Version (if applicable)
0.6.2-cuda
Operating System
Debian (Kubernetes Cluster)
Browser (if applicable)
Edge 136
Confirmation
README.md.Expected Behavior
When a Filter or Pipeline as Function raised a error message, it will be raised with "raise Exception("Rate limit exceeded. Please try again later.")"
The error message is displayed and should be displayed in the conversation.
Actual Behavior
The message raised will only be displayed once. After reloading/browser restart/relogin the message is non persistent and the conversaiton does not show the error message and keeps showing it loads the message.
Steps to Reproduce
Use any function that can raise an error/exception.
Raise an exception.
Refresh browser/relogging/restart browser
Switch to conversation.
Logs & Screenshots
See above. No error messages or non 200 HTTP Codes in Log.
Additional Information
No response
@tjbck commented on GitHub (Mar 28, 2025):
Addressed in dev!
@Xeroxxx commented on GitHub (Mar 28, 2025):
Thank you!!
Did you check with Pipelines as well? I remember just getting "Connection Lost" instead of the exception actual message. Sry forgot about that.