[GH-ISSUE #18417] issue: Final chat results won't show until browser refresh with a complex Pipe in version 0.5.x #8412 is back on .33 and .34 docker image and pip
#89332
I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I am using the latest version of Open WebUI.
Installation Method
Docker
Open WebUI Version
6.34 and 6.33 seemed fine in 6.32
Ollama Version (if applicable)
No response
Operating System
Docker Debian
Browser (if applicable)
No response
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 provided every relevant configuration, setting, and environment variable used in my setup.
I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
Start with the initial platform/version/OS and dependencies used,
Specify exact install/launch/configure commands,
List URLs visited, user input (incl. example values/emails/passwords if needed),
Describe all options and toggles enabled or changed,
Include any files or environmental changes,
Identify the expected and actual result at each stage,
Ensure any reasonably skilled user can follow and hit the same issue.
Expected Behavior
When you open a new chat or you delete one mainly when you delete one they all go away into the chat and the only way to get back is control F5 well on a phone it's kind of hard to do because it doesn't exist especially running it is a web app so to me it's something that's got to be addressed because it's had to use a different platform
Actual Behavior
The issue has apparently existed before I started using it 'cause I've seen it and then it went away and apparently it's back again I don't know why it does it with your darker image it does it on VIP installs I have it also on PowerShell through PIP and it does the same thing but 6.3 2 seemed to be fine so something changed
Steps to Reproduce
use the program i dont know how you missed it
Logs & Screenshots
not possible
Additional Information
No response
Originally created by @formytech on GitHub (Oct 18, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18417
### Check Existing Issues
- [x] I have searched for any existing and/or related issues.
- [x] I have searched for any existing and/or related discussions.
- [x] I am using the latest version of Open WebUI.
### Installation Method
Docker
### Open WebUI Version
6.34 and 6.33 seemed fine in 6.32
### Ollama Version (if applicable)
_No response_
### Operating System
Docker Debian
### Browser (if applicable)
_No response_
### 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 **provided every relevant configuration, setting, and environment variable used in my setup.**
- [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
- [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps:
- Start with the initial platform/version/OS and dependencies used,
- Specify exact install/launch/configure commands,
- List URLs visited, user input (incl. example values/emails/passwords if needed),
- Describe all options and toggles enabled or changed,
- Include any files or environmental changes,
- Identify the expected and actual result at each stage,
- Ensure any reasonably skilled user can follow and hit the same issue.
### Expected Behavior
When you open a new chat or you delete one mainly when you delete one they all go away into the chat and the only way to get back is control F5 well on a phone it's kind of hard to do because it doesn't exist especially running it is a web app so to me it's something that's got to be addressed because it's had to use a different platform
### Actual Behavior
The issue has apparently existed before I started using it 'cause I've seen it and then it went away and apparently it's back again I don't know why it does it with your darker image it does it on VIP installs I have it also on PowerShell through PIP and it does the same thing but 6.3 2 seemed to be fine so something changed
### Steps to Reproduce
use the program i dont know how you missed it
### Logs & Screenshots
not possible
### Additional Information
_No response_
GiteaMirror
added the bug label 2026-05-15 14:14:14 -05:00
<!-- gh-comment-id:3419164010 -->
@silentoplayz commented on GitHub (Oct 19, 2025):
Closing in favor of the existing linked discussion post, which is quite frankly more legible. https://github.com/open-webui/open-webui/discussions/8412
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 @formytech on GitHub (Oct 18, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18417
Check Existing Issues
Installation Method
Docker
Open WebUI Version
6.34 and 6.33 seemed fine in 6.32
Ollama Version (if applicable)
No response
Operating System
Docker Debian
Browser (if applicable)
No response
Confirmation
README.md.Expected Behavior
When you open a new chat or you delete one mainly when you delete one they all go away into the chat and the only way to get back is control F5 well on a phone it's kind of hard to do because it doesn't exist especially running it is a web app so to me it's something that's got to be addressed because it's had to use a different platform
Actual Behavior
The issue has apparently existed before I started using it 'cause I've seen it and then it went away and apparently it's back again I don't know why it does it with your darker image it does it on VIP installs I have it also on PowerShell through PIP and it does the same thing but 6.3 2 seemed to be fine so something changed
Steps to Reproduce
use the program i dont know how you missed it
Logs & Screenshots
not possible
Additional Information
No response
@silentoplayz commented on GitHub (Oct 19, 2025):
Closing in favor of the existing linked discussion post, which is quite frankly more legible. https://github.com/open-webui/open-webui/discussions/8412