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 #11652] issue: Intermittent Loss and Recovery of Subsequent Messages When Selecting Previous Conversations in Multi-Model Chats #31837

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

Originally created by @pepepaco on GitHub (Mar 13, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/11652

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.5.20

Ollama Version (if applicable)

No response

Operating System

Windows 11

Browser (if applicable)

Edge

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 listed steps to reproduce the bug in detail.

Expected Behavior

When navigating through previous conversations in a multi-model chat, the selection of a prior conversation should not alter or remove subsequent messages. All messages should remain visible and in their original order, regardless of which previous conversation is selected. New messages should always be appended to the end of the existing conversation.

Actual Behavior

Interacting with previous conversations causes inconsistent and unexpected behavior with subsequent messages, including deletion, temporary disappearance, and overwriting:

  • Scenario 1: General Selection of Previous Conversation: Selecting any previous conversation (by clicking on a message from that conversation) causes all subsequent messages to disappear.

  • Scenario 2: Partial Recovery: Selecting the first or last message of a specific, previously-selected conversation sometimes causes the disappeared subsequent messages to reappear. This is inconsistent.

  • Scenario 3: Message Overwrite:

    1. Select a previous conversation (causing subsequent messages to disappear, as in Scenario 1).
    2. While subsequent messages are hidden, send a new message.
    3. The new message does not cause the hidden messages to reappear.
    4. Now, attempt the recovery action from Scenario 2 (selecting the first/last message of the previously-selected conversation).
    5. The previously hidden messages reappear, but the new message sent in step 2 is gone (overwritten or permanently deleted).

  • Scenario 4: Successful Send:

    1. Select a previous conversation, disappearing messages after that conversation.
    2. Restore visibility of the messages by picking the first message from the prior conversation that caused the disappearing.
    3. Send the new message.
    4. The message is send normally and appears consistent in the conversation.

Steps to Reproduce

Scenario 1 (Disappearance):

  1. Start a multi-model conversation with multiple exchanges.
  2. Select a message from any previous point in the conversation (not the very last message).
  3. Observe: All messages after the selected message disappear.

Scenario 2 (Partial, Inconsistent Recovery):

  1. Follow steps 1-3 from Scenario 1 (messages disappear).
  2. Select the very first message of the conversation you selected in step 2.
  3. Observe: Sometimes, the disappeared messages reappear. Try selecting the last message of that same conversation; sometimes this also works. The behavior is unreliable.

Scenario 3 (Overwriting):

  1. Follow steps 1-3 from Scenario 1 (messages disappear).
  2. While the messages are hidden, type and send a new message.
  3. Observe: The new message is sent, but the other messages remain hidden.
  4. Attempt the recovery from Scenario 2 (selecting the first/last message).
  5. Observe: The previously disappeared messages reappear, but the new message sent in step 2 is gone.

Scenario 4 (Normal Send):

  1. Follow steps 1-3 from Scenario 1 (messages disappear).
  2. Follow the steps of Scenario 2 (message reappear).
  3. While the messages are visible, type and scend a new message.
  4. Observe: The new message is sent, and the other messages remain visible.

Logs & Screenshots

no useful information in logs.

console.log

Additional Information

Workaround: After selecting a previous conversation (or interacting with the "Copy" button on a previous message), messages after that point may disappear. To attempt to recover the missing messages before sending any new messages, try the following:

  1. First, click on the first message of the previously selected conversation (the one that caused the messages to disappear).

  2. If that doesn't work, click on the last message of that same conversation.

  3. If messages still haven't reappeared, systematically click on other message blocks within that same previously selected conversation. Specifically, try clicking on messages:

    • From different models involved in that conversation.
    • From different points within that conversation (e.g., early messages, later messages).

  4. If messages haven't reappeared continue clicking on different message blocks, this time from different models involved on the whole conversation, and not only in the previously selected conversation.

This workaround is not guaranteed to work consistently, but it has been observed to sometimes restore the visibility of the missing messages. It is crucially important to attempt this recovery before sending any new messages, as sending a new message while the others are hidden will lead to data loss (overwriting).

Originally created by @pepepaco on GitHub (Mar 13, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/11652 ### 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.5.20 ### Ollama Version (if applicable) _No response_ ### Operating System Windows 11 ### Browser (if applicable) Edge ### 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 When navigating through previous conversations in a multi-model chat, the selection of a prior conversation should *not* alter or remove subsequent messages. All messages should remain visible and in their original order, regardless of which previous conversation is selected. New messages should always be appended to the *end* of the existing conversation. ### Actual Behavior Interacting with previous conversations causes inconsistent and unexpected behavior with subsequent messages, including deletion, temporary disappearance, and overwriting: * **Scenario 1: General Selection of Previous Conversation:** Selecting *any* previous conversation (by clicking on a message from that conversation) causes all subsequent messages to *disappear*. * **Scenario 2: Partial Recovery:** Selecting the *first* or *last* message of a specific, previously-selected conversation *sometimes* causes the disappeared subsequent messages to reappear. This is inconsistent. * **Scenario 3: Message Overwrite:** 1. Select a previous conversation (causing subsequent messages to disappear, as in Scenario 1). 2. While subsequent messages are hidden, send a *new* message. 3. The new message does *not* cause the hidden messages to reappear. 4. Now, attempt the recovery action from Scenario 2 (selecting the first/last message of the previously-selected conversation). 5. The previously hidden messages *reappear*, but the new message sent in step 2 is *gone* (overwritten or permanently deleted). * **Scenario 4: Successful Send:** 1. Select a previous conversation, disappearing messages after that conversation. 2. Restore visibility of the messages by picking the first message from the prior conversation that caused the disappearing. 3. Send the new message. 4. The message is send normally and appears consistent in the conversation. ### Steps to Reproduce **Scenario 1 (Disappearance):** 1. Start a multi-model conversation with multiple exchanges. 2. Select a message from *any* previous point in the conversation (not the very last message). 3. Observe: All messages *after* the selected message disappear. **Scenario 2 (Partial, Inconsistent Recovery):** 1. Follow steps 1-3 from Scenario 1 (messages disappear). 2. Select the *very first* message of the conversation you selected in step 2. 3. Observe: Sometimes, the disappeared messages reappear. Try selecting the *last* message of that same conversation; sometimes this also works. The behavior is unreliable. **Scenario 3 (Overwriting):** 1. Follow steps 1-3 from Scenario 1 (messages disappear). 2. While the messages are hidden, type and send a *new* message. 3. Observe: The new message is sent, but the other messages remain hidden. 4. Attempt the recovery from Scenario 2 (selecting the first/last message). 5. Observe: The previously disappeared messages reappear, but the new message sent in step 2 is *gone*. **Scenario 4 (Normal Send):** 1. Follow steps 1-3 from Scenario 1 (messages disappear). 2. Follow the steps of Scenario 2 (message reappear). 3. While the messages are visible, type and scend a *new* message. 4. Observe: The new message is sent, and the other messages remain visible. ### Logs & Screenshots no useful information in logs. [console.log](https://github.com/user-attachments/files/19237483/console.log) ### Additional Information **Workaround:** After selecting a previous conversation (or interacting with the "Copy" button on a previous message), messages after that point may disappear. To *attempt* to recover the missing messages *before* sending any new messages, try the following: 1. First, click on the *first* message of the previously selected conversation (the one that caused the messages to disappear). 2. If that doesn't work, click on the *last* message of that *same* conversation. 3. If messages still haven't reappeared, systematically click on *other* message blocks within that same previously selected conversation. Specifically, try clicking on messages: * From *different models* involved in that conversation. * From different *points* within that conversation (e.g., early messages, later messages). 4. If messages haven't reappeared continue clicking on different message blocks, this time from *different models involved on the whole conversation, and not only in the previously selected conversation*. This workaround is *not* guaranteed to work consistently, but it has been observed to sometimes restore the visibility of the missing messages. It is *crucially important* to attempt this recovery *before* sending any new messages, as sending a new message while the others are hidden *will* lead to data loss (overwriting).
GiteaMirror added the bug label 2026-04-25 05:44:19 -05:00
GiteaMirror commented 2026-04-25 05:44:20 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Mar 14, 2025):

Intended behaviour, you "select" a message to continue.

<!-- gh-comment-id:2724430439 --> @tjbck commented on GitHub (Mar 14, 2025): Intended behaviour, you "select" a message to continue.
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#31837
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?