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

After building the knowledge base through the pipeline, most embedded documents remain stuck in the "queued" status, with only a minimal probability of successful embedding. #18185

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

Originally created by @MuDongliang111 on GitHub (Sep 24, 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.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

After creating a knowledge base through the knowledge pipeline, the test run in the "pipeline" works normally and produces results, and everything functions correctly. However, after publishing the "pipeline," when uploading files to the knowledge base, the files remain in the "embedding waiting" state, consistently showing as "queued" (only in very rare cases do they embed successfully, with a status of "available"). Celery does not show any runtime errors, but it also does not receive request processing information. In knowledge bases built without the knowledge pipeline, documents can be embedded normally.

Image Image Image

✔️ Expected Behavior

The knowledge base created through the knowledge pipeline can embed files normally, and the file status is "available."

❌ Actual Behavior

The knowledge base created through the knowledge pipeline can only embed files normally in very few cases; in most situations, it shows "Queued."

Originally created by @MuDongliang111 on GitHub (Sep 24, 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.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce After creating a knowledge base through the knowledge pipeline, the test run in the "pipeline" works normally and produces results, and everything functions correctly. However, after publishing the "pipeline," when uploading files to the knowledge base, the files remain in the "embedding waiting" state, consistently showing as "queued" (only in very rare cases do they embed successfully, with a status of "available"). Celery does not show any runtime errors, but it also does not receive request processing information. In knowledge bases built without the knowledge pipeline, documents can be embedded normally. <img width="2329" height="1256" alt="Image" src="https://github.com/user-attachments/assets/473d8f2e-ca2d-4721-84c1-9850a04a8559" /> <img width="2345" height="1261" alt="Image" src="https://github.com/user-attachments/assets/5107587b-1691-4d4b-993f-a53a090da429" /> <img width="2339" height="1265" alt="Image" src="https://github.com/user-attachments/assets/1fe6a0d3-9a8c-4a41-b486-dd7711e7eaea" /> ### ✔️ Expected Behavior The knowledge base created through the knowledge pipeline can embed files normally, and the file status is "available." ### ❌ Actual Behavior The knowledge base created through the knowledge pipeline can only embed files normally in very few cases; in most situations, it shows "Queued."
yindo closed this issue 2026-02-21 19:44:37 -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
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#18185
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?