[GH-ISSUE #14767] issue: #17359

New Issue

GiteaMirror · 2026-04-19T23:05:36-05:00

GiteaMirror commented

2026-04-19 23:05:36 -05:00

Originally created by @TheMoye on GitHub (Jun 7, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/14767

Check Existing Issues

I have searched the existing issues and discussions.
I am using the latest version of Open WebUI.

Installation Method

Pip Install

Open WebUI Version

v0.6.13

Ollama Version (if applicable)

v0.9.0

Operating System

Windows 11

Browser (if applicable)

Firefox 139.0.1

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 a Knowledge Base is deleted via the OpenWebUI interface, all associated uploaded documents should be removed from the data/uploads folder. Furthermore, all vectors (embeddings) generated from these documents and stored in the data/vector_db folder should be deleted.

Similarly, when individual documents are deleted from a Knowledge Base via the interface, their corresponding files should be removed from data/uploads and their associated vectors from data/vector_db.

Ideally, any modification to a Knowledge Base's parameters (such as "chunk" size) should trigger a re-generation and update of existing vectors (without creating duplicates), or provide an explicit "rebuild" option for the index.

Actual Behavior

When I delete a Knowledge Base in OpenWebUI, a green success notification appears, but the source documents in data/uploads and their associated vectors in data/vector_db are not removed and remain on disk.

The same behavior occurs when I delete individual documents within a Knowledge Base: a green success notification appears, but the files and their vectors are not deleted from the aforementioned folders.

Moreover, I observed that by opening and "saving" (without modification) each document within the Knowledge Base editor after adjusting the "chunk" size, the size of the data/vector_db folder nearly doubled. This suggests that new vectors were generated and added alongside existing ones for the same documents, instead of updating or replacing them, leading to an accumulation of redundant data.

My setup uses Ollama for embedding models (bge-m3:567m).

I think this is the same issue as here: https://github.com/open-webui/open-webui/issues/13718

Steps to Reproduce

Create a Knowledge Base and upload at least one document.
Delete the Knowledge Base via the UI.
Observe that files persist in data/uploads and data/vector_db.
Alternatively, delete an individual document from within a Knowledge Base via the UI.
Observe that the deleted document's file persists in data/uploads and its vectors in data/vector_db.

Logs & Screenshots

No specific error logs are generated during these actions. The UI displays success messages.

Additional Information

No response

Originally created by @TheMoye on GitHub (Jun 7, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/14767 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Pip Install ### Open WebUI Version v0.6.13 ### Ollama Version (if applicable) v0.9.0 ### Operating System Windows 11 ### Browser (if applicable) Firefox 139.0.1 ### 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 a Knowledge Base is deleted via the OpenWebUI interface, all associated uploaded documents should be removed from the data/uploads folder. Furthermore, all vectors (embeddings) generated from these documents and stored in the data/vector_db folder should be deleted. Similarly, when individual documents are deleted from a Knowledge Base via the interface, their corresponding files should be removed from data/uploads and their associated vectors from data/vector_db. Ideally, any modification to a Knowledge Base's parameters (such as "chunk" size) should trigger a re-generation and update of existing vectors (without creating duplicates), or provide an explicit "rebuild" option for the index. ### Actual Behavior When I delete a Knowledge Base in OpenWebUI, a green success notification appears, but the source documents in data/uploads and their associated vectors in data/vector_db are not removed and remain on disk. The same behavior occurs when I delete individual documents within a Knowledge Base: a green success notification appears, but the files and their vectors are not deleted from the aforementioned folders. Moreover, I observed that by opening and "saving" (without modification) each document within the Knowledge Base editor after adjusting the "chunk" size, the size of the data/vector_db folder nearly doubled. This suggests that new vectors were generated and added alongside existing ones for the same documents, instead of updating or replacing them, leading to an accumulation of redundant data. My setup uses Ollama for embedding models (bge-m3:567m). I think this is the same issue as here: https://github.com/open-webui/open-webui/issues/13718 ### Steps to Reproduce - Create a Knowledge Base and upload at least one document. - Delete the Knowledge Base via the UI. - Observe that files persist in data/uploads and data/vector_db. - Alternatively, delete an individual document from within a Knowledge Base via the UI. - Observe that the deleted document's file persists in data/uploads and its vectors in data/vector_db. ### Logs & Screenshots No specific error logs are generated during these actions. The UI displays success messages. ### Additional Information _No response_

GiteaMirror added the bug label 2026-04-19 23:05:36 -05:00

GiteaMirror closed this issue

2026-04-19 23:05:37 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#17359