[GH-ISSUE #23658] feat: Ability to stop knowledge directory uploads and view the current status. #20034

New Issue

GiteaMirror · 2026-04-20T02:36:59-05:00

GiteaMirror commented

2026-04-20 02:36:59 -05:00

Originally created by @brumansniffer on GitHub (Apr 13, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23658

Check Existing Issues

I have searched for all existing open AND closed issues and discussions for similar requests. I have found none that is comparable to my request.

Verify Feature Scope

I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.

Problem Description

When uploading directory of files in knowledge, in my current use I have 1570 files, mind you they are markdown files, each file takes 70s to process, and after each file is processed i get pop-up with notification and how many remaining. But.. there is no way to stop this process.. im not willing to wait 32h for all of them to finish.. ill find a faster way to do it. So this was my gripe.

Desired Solution you'd like

Ability to see like a common donwloads/uploads window of status of upload to knowledge current file / of total files, and a button to stop the process if needed.

Alternatives Considered

No response

Additional Context

Some users like me didnt know it would take this long, when adding my knowledge, so this was frustrating.

Originally created by @brumansniffer on GitHub (Apr 13, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/23658 ### Check Existing Issues - [x] I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request. ### Verify Feature Scope - [x] I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions. ### Problem Description When uploading directory of files in knowledge, in my current use I have 1570 files, mind you they are markdown files, each file takes 70s to process, and after each file is processed i get pop-up with notification and how many remaining. But.. there is no way to stop this process.. im not willing to wait 32h for all of them to finish.. ill find a faster way to do it. So this was my gripe. ### Desired Solution you'd like Ability to see like a common donwloads/uploads window of status of upload to knowledge current file / of total files, and a button to stop the process if needed. ### Alternatives Considered _No response_ ### Additional Context Some users like me didnt know it would take this long, when adding my knowledge, so this was frustrating.

GiteaMirror closed this issue

2026-04-20 02:36:59 -05:00

GiteaMirror commented

2026-04-20 02:37:00 -05:00

@Classic298 commented on GitHub (Apr 13, 2026):

should be added here for now - https://github.com/open-webui/open-webui/issues/19394

if you want faster processing you should use faster embedding model and faster document extraction engine (tika)

@Classic298 commented on GitHub (Apr 13, 2026): should be added here for now - https://github.com/open-webui/open-webui/issues/19394 if you want faster processing you should use faster embedding model and faster document extraction engine (tika)

GiteaMirror commented

2026-04-20 02:37:01 -05:00

@Classic298 commented on GitHub (Apr 13, 2026):

be aware, fast trades with quality

@Classic298 commented on GitHub (Apr 13, 2026): be aware, fast trades with quality

GiteaMirror commented

2026-04-20 02:37:01 -05:00

@brumansniffer commented on GitHub (Apr 15, 2026):

I dont know if its related but using the same llm model that i tried with open-webui, with anything-llm running vectordb = lancedb thingie, i got all my same thousands of files ingested in about 10min. but that UI also suffers the same problem with not being able to cancel the operation. Atleast it went faster. Embedding model was run on an external server in both cases.

should be added here for now - #19394

if you want faster processing you should use faster embedding model and faster document extraction engine (tika)

How is this related to this post? The problem described there is different from what im asking.

What is lacking in the webUI is when you upload a lot of files through webUI there is no way to cancel that operation and it will start to embbed them files one by one, but you cant cancel the embedding process. Its not clear for a user when will the process finish, or if its going on, unless you monitor server logs or somehting.

@brumansniffer commented on GitHub (Apr 15, 2026): I dont know if its related but using the same llm model that i tried with open-webui, with anything-llm running vectordb = lancedb thingie, i got all my same thousands of files ingested in about 10min. but that UI also suffers the same problem with not being able to cancel the operation. Atleast it went faster. Embedding model was run on an external server in both cases. > should be added here for now - [#19394](https://github.com/open-webui/open-webui/issues/19394) > > if you want faster processing you should use faster embedding model and faster document extraction engine (tika) How is this related to this post? The problem described there is different from what im asking. What is lacking in the webUI is when you upload a lot of files through webUI there is no way to cancel that operation and it will start to embbed them files one by one, but you cant cancel the embedding process. Its not clear for a user when will the process finish, or if its going on, unless you monitor server logs or somehting.

GiteaMirror commented

2026-04-20 02:37:02 -05:00

@Classic298 commented on GitHub (Apr 15, 2026):

You said

im not willing to wait 32h for all of them to finish.. ill find a faster way to do it. So this was my gripe.

and

Some users like me didnt know it would take this long

thats how its related to the post

@Classic298 commented on GitHub (Apr 15, 2026): You said > im not willing to wait 32h for all of them to finish.. ill find a faster way to do it. So this was my gripe. and > Some users like me didnt know it would take this long thats how its related to the post

GiteaMirror commented

2026-04-20 02:37:03 -05:00

@Classic298 commented on GitHub (Apr 15, 2026):

and that issue and PR is relevant because it shows the progress

Ability to see like a common donwloads/uploads window of status of upload to knowledge current file / of total files

which is exactly what you described as wanted solution

@Classic298 commented on GitHub (Apr 15, 2026): and that issue and PR is relevant because it shows the progress > Ability to see like a common donwloads/uploads window of status of upload to knowledge current file / of total files which is exactly what you described as wanted solution

GiteaMirror referenced this issue

2026-04-20 05:56:15 -05:00

[PR #20034] [CLOSED] docs: clarify docker image tagging for production use #25436

GiteaMirror referenced this issue

2026-04-25 13:23:34 -05:00

[PR #20034] [CLOSED] docs: clarify docker image tagging for production use #41066

GiteaMirror referenced this issue

2026-04-30 00:25:45 -05:00

[PR #20034] [CLOSED] docs: clarify docker image tagging for production use #48484

GiteaMirror referenced this issue

2026-05-06 09:45:48 -05:00

[PR #20034] [CLOSED] docs: clarify docker image tagging for production use #64292