issue: User Cannot Continue Chat After Error #5675

New Issue

2025-11-11T16:28:52-06:00

GiteaMirror commented

2025-11-11 16:28:52 -06:00

Originally created by @RkRamboll on GitHub (Jul 1, 2025).

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

Additional Information

No response

Originally created by @RkRamboll on GitHub (Jul 1, 2025). ### 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 2025-11-11 16:28:53 -06:00

GiteaMirror closed this issue

2025-11-11 16:28:53 -06:00

GiteaMirror commented

2025-11-11 16:28:55 -06:00

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

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

@tjbck commented on GitHub (Jul 1, 2025): Intended behaviour here, the user should delete the message instead if they wanted to continue the chat.