langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 12:05:30 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Knowledge base file stuck in 'Queuing' state (Dify cloud v1.9.1) #19174

New Issue
Closed
opened 2026-02-21 19:56:38 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 19:56:38 -05:00
Owner
Copy Link
Copy Source

Originally created by @lll322 on GitHub (Oct 13, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.1

Cloud or Self Hosted

Cloud

Steps to reproduce

  1. Go to the Knowledge Base section on the Dify cloud dashboard.
  2. Click “New Knowledge Base” and create a new one.、
  3. Upload a plain .txt file (UTF-8 without BOM, just 1).
  4. Wait and observe the file status.

✔️ Expected Behavior

The uploaded file should be processed within a few seconds, and the status should change from “Queuing” to “Completed.”

❌ Actual Behavior

The status remains “Queuing” indefinitely (even after 5 hours or more).
Refreshing the page does not help.
Tried multiple files, browsers, incognito mode, and even PC restart — all result in the same “Queuing” state.

Originally created by @lll322 on GitHub (Oct 13, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.9.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce 1. Go to the Knowledge Base section on the Dify cloud dashboard. 2. Click “New Knowledge Base” and create a new one.、 3. Upload a plain .txt file (UTF-8 without BOM, just 1). 4. Wait and observe the file status. ### ✔️ Expected Behavior The uploaded file should be processed within a few seconds, and the status should change from “Queuing” to “Completed.” ### ❌ Actual Behavior The status remains “Queuing” indefinitely (even after 5 hours or more). Refreshing the page does not help. Tried multiple files, browsers, incognito mode, and even PC restart — all result in the same “Queuing” state.
yindo added the 🐞 bugcloud labels 2026-02-21 19:56:38 -05:00
yindo closed this issue 2026-02-21 19:56:38 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label cloud 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#19174
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?