github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 19:08:59 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #18620] issue: only some (60) chats are loaded and shown in folders, rests are discarded but searchable #34185

New Issue
Closed
opened 2026-04-25 08:05:57 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-25 08:05:57 -05:00
Owner
Copy Link

Originally created by @visaes on GitHub (Oct 25, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/18620

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.34 (also exsits in v0.6.32, untested in v0.6.31)

Ollama Version (if applicable)

No response

Operating System

Debian 12/13 (both)

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

  • Open any folder with more than a significant (60) number of chats
  • All chats should be loaded under the folder

Actual Behavior

  • Only some (60) chats are loaded.

Steps to Reproduce

  • Default setup using docker compose from docs
  • docker compose up -d
  • Open any folder with more than a significant (60) number of chats
  • All chats should be loaded under the folder, but only some are loaded

Logs & Screenshots

no console errors, the issue might come from the process of reducing number of folder api calls, (like #17889 but in dev), so it was never attempted to fetch more chats under the folder.

Additional Information

Does not have this issue in v0.6.30, unsure of v0.6.31, but issue exists in v0.6.32, v0.6.34.

Originally created by @visaes on GitHub (Oct 25, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/18620 ### 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.34 (also exsits in v0.6.32, untested in v0.6.31) ### Ollama Version (if applicable) _No response_ ### Operating System Debian 12/13 (both) ### 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 - Open any folder with more than a significant (60) number of chats - All chats should be loaded under the folder ### Actual Behavior - Only some (60) chats are loaded. ### Steps to Reproduce - Default setup using docker compose from docs - `docker compose up -d` - Open any folder with more than a significant (60) number of chats - All chats should be loaded under the folder, **but only some are loaded** ### Logs & Screenshots no console errors, the issue *might* come from the process of reducing number of folder api calls, (like #17889 but in dev), so it was never attempted to fetch more chats under the folder. ### Additional Information Does not have this issue in `v0.6.30`, unsure of `v0.6.31`, but issue exists in `v0.6.32`, `v0.6.34`.
GiteaMirror added the bug label 2026-04-25 08:05:57 -05:00
GiteaMirror commented 2026-04-25 08:05:59 -05:00
Author
Owner
Copy Link

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

Intended behaviour.

<!-- gh-comment-id:3447949380 --> @tjbck commented on GitHub (Oct 26, 2025): Intended behaviour.
GiteaMirror commented 2026-04-25 08:06:00 -05:00
Author
Owner
Copy Link

@visaes commented on GitHub (Oct 26, 2025):

@tjbck I am not sure why this would be the intended behaviour? Chats are organised by projects (folders), and plenty of them are over 60 chats in each folder, the rests are basically non-accessible. (You cannot search chats using folder names and these chats would never shown in sidebar), making them basically non-organised / hidden.

<!-- gh-comment-id:3447960969 --> @visaes commented on GitHub (Oct 26, 2025): @tjbck I am not sure why this would be the intended behaviour? Chats are organised by projects (folders), and plenty of them are over 60 chats in each folder, the rests are basically non-accessible. (You cannot search chats using folder names and these chats would never shown in sidebar), making them basically non-organised / hidden.
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#34185
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?