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

After deploying the source code (including middleware), the uploaded files in the knowledge base keep showing as queued #20605

New Issue
Closed
opened 2026-02-21 20:08:08 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 20:08:08 -05:00
Owner
Copy Link
Copy Source

Originally created by @MrYangming on GitHub (Nov 27, 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.10.0

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Image Image

✔️ Expected Behavior

Normal vectorization

❌ Actual Behavior

No response

Originally created by @MrYangming on GitHub (Nov 27, 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.10.0 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce <img width="1676" height="375" alt="Image" src="https://github.com/user-attachments/assets/0143fd37-b528-44c7-866e-4635e9b4e570" /> <img width="1771" height="739" alt="Image" src="https://github.com/user-attachments/assets/0ca870b9-1cd7-4b55-8e73-8266452eea91" /> ### ✔️ Expected Behavior Normal vectorization ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:08:08 -05:00
yindo closed this issue 2026-02-21 20:08:08 -05:00
yindo commented 2026-02-21 20:08:08 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 27, 2025):

The most common reason uploaded files stay "queued" in the knowledge base is that the Celery worker isn't running or isn't subscribed to all the required queues for document processing and vectorization. For Dify v1.10.0 (source deployment), you need to make sure your worker is started with all the necessary queues, including priority_pipeline, pipeline, and priority_dataset. The recommended command is:

uv run celery -A app.celery worker -P threads -c 2 --loglevel INFO -Q dataset,mail,ops_trace,app_deletion,plugin,workflow_storage,conversation,priority_pipeline,pipeline,priority_dataset

If any of these queues are missing, files will remain stuck in "queued" status and won't be processed or vectorized example.

Also, check that Redis and your vector database (e.g., Milvus, Weaviate) are running and reachable. Make sure your .env file has DEBUG=false and FLASH_DEBUG=false, and that your embedding model API key is valid and not rate-limited example.

If the issue persists, inspect the Celery worker and API logs for errors, and check the dataset_documents, dataset_document_segments, dataset_document_queues, and dataset_document_logs tables for clues about stuck jobs example.

Let me know if you need more details on any of these steps!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 27, 2025): <!-- Answer --> The most common reason uploaded files stay "queued" in the knowledge base is that the Celery worker isn't running or isn't subscribed to all the required queues for document processing and vectorization. For Dify v1.10.0 (source deployment), you need to make sure your worker is started with all the necessary queues, including `priority_pipeline`, `pipeline`, and `priority_dataset`. The recommended command is: ``` uv run celery -A app.celery worker -P threads -c 2 --loglevel INFO -Q dataset,mail,ops_trace,app_deletion,plugin,workflow_storage,conversation,priority_pipeline,pipeline,priority_dataset ``` If any of these queues are missing, files will remain stuck in "queued" status and won't be processed or vectorized [example](https://github.com/langgenius/dify/issues/28077). Also, check that Redis and your vector database (e.g., Milvus, Weaviate) are running and reachable. Make sure your `.env` file has `DEBUG=false` and `FLASH_DEBUG=false`, and that your embedding model API key is valid and not rate-limited [example](https://github.com/langgenius/dify/issues/26171). If the issue persists, inspect the Celery worker and API logs for errors, and check the `dataset_documents`, `dataset_document_segments`, `dataset_document_queues`, and `dataset_document_logs` tables for clues about stuck jobs [example](https://github.com/langgenius/dify/issues/26374). Let me know if you need more details on any of these steps! <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/e2c37627-730f-48e8-9fe0-241ad319a421?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e2c37627-730f-48e8-9fe0-241ad319a421?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e2c37627-730f-48e8-9fe0-241ad319a421?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e2c37627-730f-48e8-9fe0-241ad319a421?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e2c37627-730f-48e8-9fe0-241ad319a421?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e2c37627-730f-48e8-9fe0-241ad319a421?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e2c37627-730f-48e8-9fe0-241ad319a421?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20most%20common%20reason%20uploaded%20files%20stay%20%22queued%22%20in%20the%20knowledge%20base%20is%20that%20the%20Celery%20worker%20isn%27t%20running%20or%20isn%27t%20subscribed%20to%20all%20the%20required%20queues%20for%20document%20processing%20and%20vectorization.%20For%20Dify%20v1.10.0%20%28source%20deployment%29%2C%20you%20need%20to%20make%20sure%20your%20worker%20is%20started%20with%20all%20the%20necessary%20queues%2C%20including%20%60priority_pipeline%60%2C%20%60pipeline%60%2C%20and%20%60priority_dataset%60.%20The%20recommended%20command%20is%3A%0A%0A%60%60%60%0Auv%20run%20celery%20-A%20app.celery%20worker%20-P%20threads%20-c%202%20--loglevel%20INFO%20-Q%20dataset%2Cmail%2Cops_trace%2Capp_deletion%2Cplugin%2Cworkflow_storage%2Cconversation%2Cpriority_pipeline%2Cpipeline%2Cpriority_dataset%0A%60%60%60%0A%0AIf%20any%20of%20these%20queues%20are%20missing%2C%20files%20will%20remain%20stuck%20in%20%22queued%22%20status%20and%20won%27t%20be%20processed%20or%20vectorized%C2%A0%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/28077%29.%0A%0AAlso%2C%20check%20that%20Redis%20and%20your%20vector%20database%20%28e.g.%2C%20Milvus%2C%20Weaviate%29%20are%20running%20and%20reachable.%20Make%20sure%20your%20%60.env%60%20file%20has%20%60DEBUG%3Dfalse%60%20and%20%60FLASH_DEBUG%3Dfalse%60%2C%20and%20that%20your%20embedding%20model%20API%20key%20is%20valid%20and%20not%20rate-limited%C2%A0%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/26171%29.%0A%0AIf%20the%20issue%20persists%2C%20inspect%20the%20Celery%20worker%20and%20API%20logs%20for%20errors%2C%20and%20check%20the%20%60dataset_documents%60%2C%20%60dataset_document_segments%60%2C%20%60dataset_document_queues%60%2C%20and%20%60dataset_document_logs%60%20tables%20for%20clues%20about%20stuck%20jobs%C2%A0%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/26374%29.%0A%0ALet%20me%20know%20if%20you%20need%20more%20details%20on%20any%20of%20these%20steps%21)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28773)
yindo commented 2026-02-21 20:08:08 -05:00
Author
Owner
Copy Link
Copy Source

@MrYangming commented on GitHub (Nov 27, 2025):

Solved, previously used commands from the official website source code deployment- uv run celery -A app.celery worker -P gevent -c 1 --loglevel INFO -Q dataset,generation,mail,ops_trace， Do we need to update the commands on the official website?

@MrYangming commented on GitHub (Nov 27, 2025): Solved, previously used commands from the official website source code deployment- uv run celery -A app.celery worker -P gevent -c 1 --loglevel INFO -Q dataset,generation,mail,ops_trace， Do we need to update the commands on the official website?
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 🐞 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#20605
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?