github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-07 03:18:23 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #19190] issue: Synchronization with Folder Leads to Empty Knowledge Base #34331

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

Originally created by @flefevre on GitHub (Nov 14, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/19190

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

Git Clone

Open WebUI Version

v0.6.34

Ollama Version (if applicable)

No response

Operating System

Ubuntu 22.04

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

I am using Milvus vector database

Expected Behavior

When synchronizing a knowledge base with a folder containing pre-existing files:

  • The system should detect and report duplicate files (if any).
  • After synchronization, the UI should display all files (including new and existing ones) in the knowledge base.
  • If a file already exists in the knowledge base, uploading it again should be detected as a duplicate, but the existing file should remain visible.

Actual Behavior

Actual Behavior

  • If synchronization is interrupted (e.g., due to an error or manual cancellation), the knowledge base appears completely empty in the UI.
  • Despite this, if a user tries to upload a file that was previously in the knowledge base, the system correctly detects it as a duplicate (indicating the file still exists in the backend).
  • The UI does not reflect the actual state of the knowledge base, making it seem like no files were synced.

Steps to Reproduce

Steps to Reproduce

  1. Create a knowledge base in Open WebUI.
  2. Upload 10 files to it and verify that all 10 files appear in the UI.
  3. Synchronize the knowledge base with a folder containing 12 files (10 identical to the existing ones + 2 new ones).
  4. Observe the result:
    • If synchronization completes successfully, the UI should show all 12 files.
    • If synchronization is interrupted (e.g., by closing the app or network issues), the UI will show an empty knowledge base, even though files still exist in the backend.
    • Attempting to upload any of the original 10 files will correctly report them as duplicates, proving they were not lost.

Logs & Screenshots

Image

Additional Information

Additional Notes

  • The issue suggests a UI state mismatch where the frontend does not reflect the actual backend state after a failed sync.
  • This could be related to:
    • Improper error handling during sync.
    • Missing UI updates when sync fails.
    • Incorrect file metadata management in the knowledge base.
  • bad links between openwebui database and milvus database

Request

Please investigate and fix this issue to ensure:

  • Synchronization failures do not result in an empty UI.
  • The knowledge base state is accurately reflected in the UI at all times.
Originally created by @flefevre on GitHub (Nov 14, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/19190 ### 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 Git Clone ### Open WebUI Version v0.6.34 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 22.04 ### 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 I am using Milvus vector database ## Expected Behavior When synchronizing a knowledge base with a folder containing pre-existing files: - The system should detect and report duplicate files (if any). - After synchronization, the UI should display all files (including new and existing ones) in the knowledge base. - If a file already exists in the knowledge base, uploading it again should be detected as a duplicate, but the existing file should remain visible. ### Actual Behavior ## Actual Behavior - If synchronization is interrupted (e.g., due to an error or manual cancellation), the knowledge base appears **completely empty** in the UI. - Despite this, if a user tries to upload a file that was previously in the knowledge base, the system correctly detects it as a duplicate (indicating the file still exists in the backend). - The UI does not reflect the actual state of the knowledge base, making it seem like no files were synced. ### Steps to Reproduce ## Steps to Reproduce 1. **Create a knowledge base** in Open WebUI. 2. **Upload 10 files** to it and verify that all 10 files appear in the UI. 3. **Synchronize the knowledge base** with a folder containing **12 files** (10 identical to the existing ones + 2 new ones). 4. **Observe the result**: - If synchronization completes successfully, the UI should show all 12 files. - If synchronization is **interrupted** (e.g., by closing the app or network issues), the UI will show an **empty knowledge base**, even though files still exist in the backend. - Attempting to upload any of the original 10 files will correctly report them as duplicates, proving they were not lost. ### Logs & Screenshots <img width="500" height="411" alt="Image" src="https://github.com/user-attachments/assets/209a3832-4227-47a8-98e3-1e3aad91430f" /> ### Additional Information ## Additional Notes - The issue suggests a **UI state mismatch** where the frontend does not reflect the actual backend state after a failed sync. - This could be related to: - Improper error handling during sync. - Missing UI updates when sync fails. - Incorrect file metadata management in the knowledge base. - bad links between openwebui database and milvus database ## Request Please investigate and fix this issue to ensure: - Synchronization failures do not result in an empty UI. - The knowledge base state is accurately reflected in the UI at all times.
GiteaMirror added the bugconfirmed issue labels 2026-04-25 08:16:20 -05:00
GiteaMirror commented 2026-04-25 08:16:22 -05:00
Author
Owner
Copy Link

@flefevre commented on GitHub (Nov 17, 2025):

I have a very much simplier test:

  • just add a new knowledge base
  • add two filme fileA and fileB
  • if you try to upload the same fileA it will detect and say "duplicate content"
  • if you delete the fileA,
  • and then try to import again the fileA, it should allow to do it: baddly it is not the case.
  • it is like you have a ghost fileA
<!-- gh-comment-id:3542479495 --> @flefevre commented on GitHub (Nov 17, 2025): I have a very much simplier test: - just add a new knowledge base - add two filme fileA and fileB - if you try to upload the same fileA it will detect and say "duplicate content" - if you delete the fileA, - and then try to import again the fileA, it should allow to do it: baddly it is not the case. - it is like you have a ghost fileA
GiteaMirror commented 2026-04-25 08:16:22 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Dec 6, 2025):

Although the behavior of the issue seems to have changed, an issue still persists. After receiving a Duplicate Content notification toast when attempting to re-upload File A, deleting the original file A removes only one instance of the file from the knowledge. However, the file remains accessible in the knowledgebase after seeing File deleted successfully, suggesting the 2nd File upload attempt may have actually succeeded, despite the Duplicate Content error notification toast.

<!-- gh-comment-id:3621286863 --> @silentoplayz commented on GitHub (Dec 6, 2025): Although the behavior of the issue seems to have changed, an issue still persists. After receiving a `Duplicate Content` notification toast when attempting to re-upload File A, deleting the original file A removes only one instance of the file from the knowledge. However, the file remains accessible in the knowledgebase after seeing `File deleted successfully`, suggesting the 2nd File upload attempt may have actually succeeded, despite the `Duplicate Content` error notification toast.
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 confirmed issue
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#34331
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?