github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 11:28:35 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #15415] issue: User Cannot Continue Chat After Error #17562

New Issue
Closed
opened 2026-04-19 23:21:12 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-19 23:21:12 -05:00
Owner
Copy Link

Originally created by @RkRamboll on GitHub (Jul 1, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/15415

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

v0.6.15

Ollama Version (if applicable)

No response

Operating System

Windows 10 Enterprise

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

Upon encountering an error, the user should be able to continue the existing chat session, ideally by retrying the last action, correcting input, or receiving guidance on how to proceed.

Actual Behavior

When an error occurs (e.g., an API error, malformed input, server issue), the chat becomes unresponsive or "stuck." The user cannot send new messages or interact further within that specific chat thread. To resume interaction, the user must initiate a completely new chat.

Steps to Reproduce

  • Add this function in the code (that will trigger the error)

      class Pipe:

      def pipe(self, body: dict) -> str:

          raise Exception

  • Now start a chat and observe that the chat session becomes unresponsive.

  • Attempt to send a new message in the same chat.

  • Note that the message is not sent, or no further interaction is possible within that chat.

Logs & Screenshots

Image

Additional Information

No response

Originally created by @RkRamboll on GitHub (Jul 1, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/15415 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version v0.6.15 ### Ollama Version (if applicable) _No response_ ### Operating System Windows 10 Enterprise ### 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 Upon encountering an error, the user should be able to continue the existing chat session, ideally by retrying the last action, correcting input, or receiving guidance on how to proceed. ### Actual Behavior When an error occurs (e.g., an API error, malformed input, server issue), the chat becomes unresponsive or "stuck." The user cannot send new messages or interact further within that specific chat thread. To resume interaction, the user must initiate a completely new chat. ### Steps to Reproduce - Add this function in the code (that will trigger the error) class Pipe: def pipe(self, body: dict) -> str: raise Exception - Now start a chat and observe that the chat session becomes unresponsive. - Attempt to send a new message in the same chat. - Note that the message is not sent, or no further interaction is possible within that chat. ### Logs & Screenshots ![Image](https://github.com/user-attachments/assets/39d1db7d-13ba-4c21-b52a-9d34887fa858) ### Additional Information _No response_
GiteaMirror added the bug label 2026-04-19 23:21:12 -05:00
GiteaMirror commented 2026-04-19 23:21:15 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Jul 1, 2025):

Intended behaviour here, the user should delete the message instead if they wanted to continue the chat.

<!-- gh-comment-id:3023713794 --> @tjbck commented on GitHub (Jul 1, 2025): Intended behaviour here, the user should delete the message instead if they wanted to continue the chat.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#17562
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?