github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-11 18:43:44 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #18327] issue: Pagination Bug After Archiving Chat: Requests page=2 Instead of Staying on page=1, Causing Empty History List #105558

New Issue
Closed
opened 2026-05-18 03:36:27 -05:00 by GiteaMirror · 7 comments
GiteaMirror commented 2026-05-18 03:36:27 -05:00
Owner
Copy Link

Originally created by @Randark-JMT on GitHub (Oct 14, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18327

Check Existing Issues

  • 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

v0.6.33

Ollama Version (if applicable)

No response

Operating System

Ubuntu 22.04

Browser (if applicable)

FIrefox Developer 144.0b9

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

After archiving a chat, the interface should remain on the current page (e.g., page=1) and reload the list to reflect the updated state

Actual Behavior

After archiving, the frontend incorrectly requests page=2, causing the chat history to appear empty or incomplete if that page has no data

Steps to Reproduce

  1. Open Open WebUI and ensure the chat history panel is visible (default request: /api/v1/chats/?page=1).
  2. Click the “Archive” button on any conversation.
  3. Open browser DevTools → Network tab.
  4. Observe that the subsequent chat list request is sent to /api/v1/chats/?page=2 instead of staying on page=1.
    If page 2 contains no conversations, the UI may display an empty list

Logs & Screenshots

In Browser

Image

No information in browser console

Docker container log

Image

Additional Information

No response

Originally created by @Randark-JMT on GitHub (Oct 14, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18327 ### 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 v0.6.33 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 22.04 ### Browser (if applicable) FIrefox Developer 144.0b9 ### 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 After archiving a chat, the interface should remain on the current page (e.g., page=1) and reload the list to reflect the updated state ### Actual Behavior After archiving, the frontend incorrectly requests page=2, causing the chat history to appear empty or incomplete if that page has no data ### Steps to Reproduce 1. Open Open WebUI and ensure the chat history panel is visible (default request: /api/v1/chats/?page=1). 2. Click the “Archive” button on any conversation. 3. Open browser DevTools → Network tab. 4. Observe that the subsequent chat list request is sent to /api/v1/chats/?page=2 instead of staying on page=1. If page 2 contains no conversations, the UI may display an empty list ### Logs & Screenshots In Browser <img width="2560" height="1335" alt="Image" src="https://github.com/user-attachments/assets/c9f2647f-d886-4ac5-91e7-5520458a61e4" /> No information in browser console Docker container log <img width="2560" height="1371" alt="Image" src="https://github.com/user-attachments/assets/550d0c40-46d3-4fe7-a938-3081945ed828" /> ### Additional Information _No response_
GiteaMirror added the bug label 2026-05-18 03:36:27 -05:00
GiteaMirror commented 2026-05-18 03:36:29 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Oct 14, 2025):

This bug has also been reported in the Open WebUI Discord server, but I will leave this issue open until it can be closed out with a PR or the maintainer addresses the issue.

Image Image Image
<!-- gh-comment-id:3403158611 --> @silentoplayz commented on GitHub (Oct 14, 2025): This bug has also been reported in the Open WebUI Discord server, but I will leave this issue open until it can be closed out with a PR or the maintainer addresses the issue. <img width="1920" height="1324" alt="Image" src="https://github.com/user-attachments/assets/fd911304-ea0b-40e4-9b8c-2a530f41eb2b" /> <img width="1920" height="1324" alt="Image" src="https://github.com/user-attachments/assets/d841bb6b-4740-47bc-812b-d6515a7b892e" /> <img width="1920" height="1324" alt="Image" src="https://github.com/user-attachments/assets/ea241e9e-54be-449e-bb17-3b1a12cbbad5" />
GiteaMirror commented 2026-05-18 03:36:29 -05:00
Author
Owner
Copy Link

@medexpertpingyibbs commented on GitHub (Oct 22, 2025):

ps: on smartphone, like safari of ios, or chrome of android, chat history always disappeared automatically in portrait mode for new users(vertical mode is ok), must refresh the whole page to show them again

<!-- gh-comment-id:3432410338 --> @medexpertpingyibbs commented on GitHub (Oct 22, 2025): ps: on smartphone, like safari of ios, or chrome of android, chat history always disappeared automatically in portrait mode for new users(vertical mode is ok), must refresh the whole page to show them again
GiteaMirror commented 2026-05-18 03:36:29 -05:00
Author
Owner
Copy Link

@lenz1111 commented on GitHub (Oct 23, 2025):

I was able to replicate an issue and I created fix there:
https://github.com/open-webui/open-webui/issues/18377#issuecomment-3436684323

<!-- gh-comment-id:3436698451 --> @lenz1111 commented on GitHub (Oct 23, 2025): I was able to replicate an issue and I created fix there: [https://github.com/open-webui/open-webui/issues/18377#issuecomment-3436684323](https://github.com/open-webui/open-webui/issues/18377#issuecomment-3436684323)
GiteaMirror commented 2026-05-18 03:36:31 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Oct 23, 2025):

@lenz1111 has opened up a fix PR; testing is wanted - https://github.com/open-webui/open-webui/pull/18539

<!-- gh-comment-id:3437234117 --> @silentoplayz commented on GitHub (Oct 23, 2025): @lenz1111 has opened up a fix PR; testing is wanted - https://github.com/open-webui/open-webui/pull/18539
GiteaMirror commented 2026-05-18 03:36:31 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Oct 28, 2025):

@silentoplayz could you confirm if the issue has been resolved in the latest dev?

<!-- gh-comment-id:3458450819 --> @tjbck commented on GitHub (Oct 28, 2025): @silentoplayz could you confirm if the issue has been resolved in the latest dev?
GiteaMirror commented 2026-05-18 03:36:32 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Oct 28, 2025):

I was unable to reproduce this issue on my end.

<!-- gh-comment-id:3458460247 --> @silentoplayz commented on GitHub (Oct 28, 2025): I was unable to reproduce this issue on my end.
GiteaMirror commented 2026-05-18 03:36:32 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Oct 28, 2025):

Perhaps this is browser specifc?

<!-- gh-comment-id:3458479428 --> @tjbck commented on GitHub (Oct 28, 2025): Perhaps this is browser specifc?
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#105558
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?