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

Perpetual queue for uploading a document to the knowledge base #7325

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

Originally created by @larkinmd7 on GitHub (Dec 20, 2024).

Originally assigned to: @JohnJyong on GitHub.

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.13.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

image previously uploaded documents, they were uploaded immediately and were available within 1-2 minutes. Now for some reason the documents are loaded immediately, but are constantly in the queue, without changes, although the document is the same, the settings are the same, I do not understand why this happens, what should I check to fix this bug?

✔️ Expected Behavior

❌ Actual Behavior

Originally created by @larkinmd7 on GitHub (Dec 20, 2024). Originally assigned to: @JohnJyong on GitHub. ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.13.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1674" alt="image" src="https://github.com/user-attachments/assets/88082697-c2a9-4834-a96d-b56a75012ef9" /> previously uploaded documents, they were uploaded immediately and were available within 1-2 minutes. Now for some reason the documents are loaded immediately, but are constantly in the queue, without changes, although the document is the same, the settings are the same, I do not understand why this happens, what should I check to fix this bug? ### ✔️ Expected Behavior - ### ❌ Actual Behavior -
yindo added the 🐞 bugstale labels 2026-02-21 18:20:00 -05:00
yindo closed this issue 2026-02-21 18:20:00 -05:00
yindo commented 2026-02-21 18:20:01 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 20, 2024):

I found some similar threads that might help you resolve the issue of documents remaining perpetually queued in the Dify knowledge base:

  1. Documents in queue: This issue was resolved by modifying the .env file to set the LOG_FILE path, which helped in diagnosing the problem [1].

  2. Queuing doesn't stop at Dify: This is an open discussion where users are experiencing similar issues with documents being stuck in the queue [2].

  3. 我添加的知识库的文件一直是在排队中是怎么回事啊？: Another open discussion about files remaining in the queue [3].

To address your issue, consider the following steps:

  • Rate Limit for Embedding Model API Key: Check if the rate limit for your Embedding model API key has been reached, as this can cause documents to remain queued [4].

  • Celery Worker Service: Ensure the Celery worker service is running correctly. You can start it with docker compose up -d worker and check the logs for any errors [4].

  • Service Status: Verify that all necessary services are running using docker compose ps. Ensure services like api, worker, web, weaviate, db, redis, and nginx are all up [4].

  • Pending Processes and Configuration: Check for any pending segmentation or embedding processes, and ensure all dependencies and services like db and redis are running smoothly [4].

These steps should help resolve the issue of documents being stuck in the queued state.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Dec 20, 2024): <!-- Answer --> I found some similar threads that might help you resolve the issue of documents remaining perpetually queued in the Dify knowledge base: 1. **[Documents in queue](https://github.com/langgenius/dify/discussions/10602#discussioncomment-11228040)**: This issue was resolved by modifying the `.env` file to set the `LOG_FILE` path, which helped in diagnosing the problem <sup>[[1]](https://github.com/langgenius/dify/discussions/10602)</sup>. 2. **[Queuing doesn't stop at Dify](https://github.com/langgenius/dify/discussions/10677)**: This is an open discussion where users are experiencing similar issues with documents being stuck in the queue <sup>[[2]](https://github.com/langgenius/dify/discussions/10677)</sup>. 3. **[我添加的知识库的文件一直是在排队中是怎么回事啊？](https://github.com/langgenius/dify/discussions/10617)**: Another open discussion about files remaining in the queue <sup>[[3]](https://github.com/langgenius/dify/discussions/10617)</sup>. To address your issue, consider the following steps: - **Rate Limit for Embedding Model API Key**: Check if the rate limit for your Embedding model API key has been reached, as this can cause documents to remain queued <sup>[[4]](https://github.com/langgenius/dify/issues/11657)</sup>. - **Celery Worker Service**: Ensure the Celery worker service is running correctly. You can start it with `docker compose up -d worker` and check the logs for any errors <sup>[[4]](https://github.com/langgenius/dify/issues/11657)</sup>. - **Service Status**: Verify that all necessary services are running using `docker compose ps`. Ensure services like `api`, `worker`, `web`, `weaviate`, `db`, `redis`, and `nginx` are all up <sup>[[4]](https://github.com/langgenius/dify/issues/11657)</sup>. - **Pending Processes and Configuration**: Check for any pending segmentation or embedding processes, and ensure all dependencies and services like `db` and `redis` are running smoothly <sup>[[4]](https://github.com/langgenius/dify/issues/11657)</sup>. These steps should help resolve the issue of documents being stuck in the queued state. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/c2677b43-6dcf-4411-87b6-787fde5a621a?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/c2677b43-6dcf-4411-87b6-787fde5a621a?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/c2677b43-6dcf-4411-87b6-787fde5a621a?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/c2677b43-6dcf-4411-87b6-787fde5a621a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c2677b43-6dcf-4411-87b6-787fde5a621a?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/c2677b43-6dcf-4411-87b6-787fde5a621a?feedback_type=other)</sup>
yindo commented 2026-02-21 18:20:01 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 20, 2024):

Can you attach those documents?

@crazywoola commented on GitHub (Dec 20, 2024): Can you attach those documents?
yindo commented 2026-02-21 18:20:01 -05:00
Author
Owner
Copy Link
Copy Source

@OrWestSide commented on GitHub (Dec 28, 2024):

I am facing the same issue. Documents are stuck in "Queuing".

  • Cloud version
  • Using the API

image

@OrWestSide commented on GitHub (Dec 28, 2024): I am facing the same issue. Documents are stuck in "Queuing". * Cloud version * Using the API ![image](https://github.com/user-attachments/assets/3935598b-92df-4ca2-a6ac-de3f283bff14)
yindo commented 2026-02-21 18:20:01 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jan 8, 2025):

@OrWestSide Do you still have this problem?

@crazywoola commented on GitHub (Jan 8, 2025): @OrWestSide Do you still have this problem?
yindo commented 2026-02-21 18:20:01 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 8, 2025):

Hi, @larkinmd7. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary:

  • You reported a bug in the self-hosted Docker version 0.13.1 where documents remain queued without processing.
  • I suggested troubleshooting steps, including checking the Embedding model API key rate limit and ensuring all services are running.
  • Crazywoola requested document attachments, and OrWestSide mentioned a similar issue with the cloud version.
  • Crazywoola followed up with OrWestSide to check if the issue persists.

Next Steps:

  • Please confirm if this issue is still relevant to the latest version of the Dify repository. If so, you can keep the discussion open by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 8, 2025): Hi, @larkinmd7. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary:** - You reported a bug in the self-hosted Docker version 0.13.1 where documents remain queued without processing. - I suggested troubleshooting steps, including checking the Embedding model API key rate limit and ensuring all services are running. - Crazywoola requested document attachments, and OrWestSide mentioned a similar issue with the cloud version. - Crazywoola followed up with OrWestSide to check if the issue persists. **Next Steps:** - Please confirm if this issue is still relevant to the latest version of the Dify repository. If so, you can keep the discussion open by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 18:20:01 -05:00
Author
Owner
Copy Link
Copy Source

@948024326 commented on GitHub (Feb 12, 2025):

@OrWestSide Do you still have this problem?

i still have

@948024326 commented on GitHub (Feb 12, 2025): > [@OrWestSide](https://github.com/OrWestSide) Do you still have this problem? i still have
yindo commented 2026-02-21 18:20:01 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 16, 2025):

Hi, @larkinmd7. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • You reported an issue with documents being stuck in the queue on the self-hosted Dify version 0.13.1.
  • I suggested checking the rate limit for the Embedding model API key and ensuring all services are running.
  • Crazywoola requested document attachments for further investigation.
  • OrWestSide mentioned experiencing a similar issue with the cloud version.
  • 948024326 confirmed the issue persists for them.

Next Steps

  • Please confirm if this issue is still relevant with the latest version of Dify. If so, you can keep the discussion open by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Mar 16, 2025): Hi, @larkinmd7. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - You reported an issue with documents being stuck in the queue on the self-hosted Dify version 0.13.1. - I suggested checking the rate limit for the Embedding model API key and ensuring all services are running. - Crazywoola requested document attachments for further investigation. - OrWestSide mentioned experiencing a similar issue with the cloud version. - 948024326 confirmed the issue persists for them. **Next Steps** - Please confirm if this issue is still relevant with the latest version of Dify. If so, you can keep the discussion open by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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 stale 🐞 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#7325
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?