Originally created by @brainboutique on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14089
### 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
v0.6.10
### Ollama Version (if applicable)
v0.6.5
### Operating System
Linux
### Browser (if applicable)
Chrome
### 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
On /admin/settings, I would expect the RELEVANCE_THRESHOLD to be resettable to "null" (not 0).
Reason: I suspect that a tool call returns a unknown relevance and therefore is skipped while re-ranking
### Actual Behavior
Keeps old value.
### Steps to Reproduce
1. Open settings
2. Clear out field
3. Save
4. F5 to reload OR check server response in developer tools.
### Logs & Screenshots
/api/v1/retrieval/config/update
Request payload (as copied from developer console)
{
"status": true,
...
"RELEVANCE_THRESHOLD": null,
...
}
Response payload (as copied from developer console)
{
"status": true,
...
"RELEVANCE_THRESHOLD": 0.0,
...
}
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-13 03:41:24 -05:00
@brainboutique commented on GitHub (May 20, 2025):
@tjbck then how to disable threshold filtering? "0" apparently has different semantics.
<!-- gh-comment-id:2894937448 -->
@brainboutique commented on GitHub (May 20, 2025):
@tjbck then how to disable threshold filtering? "0" apparently has different semantics.
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 @brainboutique on GitHub (May 20, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14089
Check Existing Issues
Installation Method
Docker
Open WebUI Version
v0.6.10
Ollama Version (if applicable)
v0.6.5
Operating System
Linux
Browser (if applicable)
Chrome
Confirmation
README.md.Expected Behavior
On /admin/settings, I would expect the RELEVANCE_THRESHOLD to be resettable to "null" (not 0).
Reason: I suspect that a tool call returns a unknown relevance and therefore is skipped while re-ranking
Actual Behavior
Keeps old value.
Steps to Reproduce
Logs & Screenshots
/api/v1/retrieval/config/update
Request payload (as copied from developer console)
{
"status": true,
...
"RELEVANCE_THRESHOLD": null,
...
}
Response payload (as copied from developer console)
{
"status": true,
...
"RELEVANCE_THRESHOLD": 0.0,
...
}
Additional Information
No response
@tjbck commented on GitHub (May 20, 2025):
r_score must be a float.
@brainboutique commented on GitHub (May 20, 2025):
@tjbck then how to disable threshold filtering? "0" apparently has different semantics.