[GH-ISSUE #19533] issue: Frontend infinite loading caused by malformed "500 Error" node in chat history

Originally created by @GSAlex on GitHub (Nov 27, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/19533 ### 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 have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.40 ### Ollama Version (if applicable) n/a ### Operating System debian ### Browser (if applicable) Firefox 145 ### 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 clicking on the chat in the sidebar, the interface should load and display the existing conversation history properly. ### Actual Behavior The frontend gets stuck on the loading screen. Inspecting the data reveals that the currentId points to a node that has only a error property ### Steps to Reproduce This issue occurs sporadically. It happens like that when a chat session encounters an intermittent backend 500 error during response generation. I cannot reliably reproduce the specific network/server condition that triggers the 500 error on demand. ### Logs & Screenshots Here is the minimal reproduction JSON structure extracted from the network log and database. The node 24a0acbd-9f7f-422a-b484-95ded47d368a is the cause of the crash. { "id": "c0e57f37-0fcc-4a93-b684-9716e11cb1cd", "chat": { "history": { "messages": { "2ab036cb-c726-47fa-8e55-0f57597b1517": { "id": "2ab036cb-c726-47fa-8e55-0f57597b1517", "parentId": "a1b3f9ec-35ca-4e00-a8bc-7126a80782ce", "childrenIds": [], "role": "assistant", "content": "[VALID PREVIOUS CONTENT REDACTED]", "done": true }, "24a0acbd-9f7f-422a-b484-95ded47d368a": { "error": { "content": "500: Open WebUI: Server Connection Error" } // MISSING: "role", "id", "parentId", "timestamp" } }, "currentId": "24a0acbd-9f7f-422a-b484-95ded47d368a" } } } <img width="1444" height="724" alt="Image" src="https://github.com/user-attachments/assets/e0f6a3ac-eb87-4a3b-8f2b-bb43344b3834" /> ### Additional Information Workaround: Manually editing the JSON to delete the malformed node (24a0acbd...) and reverting currentId to the previous valid node (2ab036cb...) restores access to the chat. Title Generation: The auto-title generation feature also seems to fail on this chat, presumably because the parser crashes when encountering the structureless node.

GiteaMirror commented

2026-05-18 04:04:20 -05:00

Owner

Originally created by @GSAlex on GitHub (Nov 27, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19533

Check Existing Issues

I have searched for any existing and/or related issues.
I have searched for any existing and/or related discussions.
I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.40

Ollama Version (if applicable)

n/a

Operating System

debian

Browser (if applicable)

Firefox 145

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 clicking on the chat in the sidebar, the interface should load and display the existing conversation history properly.

Actual Behavior

The frontend gets stuck on the loading screen.

Inspecting the data reveals that the currentId points to a node that has only a error property

Steps to Reproduce

This issue occurs sporadically. It happens like that when a chat session encounters an intermittent backend 500 error during response generation. I cannot reliably reproduce the specific network/server condition that triggers the 500 error on demand.

Logs & Screenshots

Here is the minimal reproduction JSON structure extracted from the network log and database. The node 24a0acbd-9f7f-422a-b484-95ded47d368a is the cause of the crash.

{
"id": "c0e57f37-0fcc-4a93-b684-9716e11cb1cd",
"chat": {
"history": {
"messages": {
"2ab036cb-c726-47fa-8e55-0f57597b1517": {
"id": "2ab036cb-c726-47fa-8e55-0f57597b1517",
"parentId": "a1b3f9ec-35ca-4e00-a8bc-7126a80782ce",
"childrenIds": [],
"role": "assistant",
"content": "[VALID PREVIOUS CONTENT REDACTED]",
"done": true
},
"24a0acbd-9f7f-422a-b484-95ded47d368a": {
"error": {
"content": "500: Open WebUI: Server Connection Error"
}
// MISSING: "role", "id", "parentId", "timestamp"
}
},
"currentId": "24a0acbd-9f7f-422a-b484-95ded47d368a"
}
}
}

Additional Information

Workaround: Manually editing the JSON to delete the malformed node (24a0acbd...) and reverting currentId to the previous valid node (2ab036cb...) restores access to the chat.

Title Generation: The auto-title generation feature also seems to fail on this chat, presumably because the parser crashes when encountering the structureless node.

GiteaMirror added the bug label 2026-05-18 04:04:20 -05:00

GiteaMirror closed this issue

2026-05-18 04:04:22 -05:00

2026-05-18 04:04:24 -05:00

Author

@tjbck commented on GitHub (Nov 27, 2025):

#19225

@tjbck commented on GitHub (Nov 27, 2025): #19225

[GH-ISSUE #19533] issue: Frontend infinite loading caused by malformed "500 Error" node in chat history #105911