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

The knowledge base files have been waiting in line since they were uploaded. #5271

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

Originally created by @PsycheJ on GitHub (Aug 28, 2024).

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.7.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Before you can use it, recently I do not know what reason has been in the queue, the docker log did not see the error report information, only has been getting the index state.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @PsycheJ on GitHub (Aug 28, 2024). ### 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.7.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Before you can use it, recently I do not know what reason has been in the queue, the docker log did not see the error report information, only has been getting the index state. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 18:10:12 -05:00
yindo commented 2026-02-21 18:10:12 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 28, 2024):

Hello @PsycheJ! I'm here to help you with any bugs, questions, or contributions you may have for the repository. Let me know how I can assist you!

I found some similar issues and discussions that might help:

  1. Issue #7675 (closed): The suggested solution was to check if the rate limit has been reached for the Embedding model API key used. Ensure the API key's rate limits are not exceeded, check for any constraints or limits, and verify that all necessary services, including the Celery worker service, are running correctly [1].

  2. Issue #7263 (closed): This issue was related to files being stuck in the "Queuing" status. The solution involved checking the rate limit for the Embedding model API key and ensuring the worker service is running correctly [2].

  3. Discussion #3283: This discussion also addresses the issue of files being stuck in the queue and suggests similar solutions [3].

For your specific case, ensure that the asynchronous queue worker is started by setting the MODE environment variable to worker in your Docker setup. Here is an example configuration for your Docker Compose file:

services:
  worker:
    image: your-docker-image
    environment:
      - MODE=worker
    ...

Without this configuration, the queue worker will not start, and the files will remain stuck in the queue [4].

Additionally, check the rate limits for the Embedding model API key and ensure they are not exceeded. You can refer to the OpenAI official documentation for details on rate limits and how to manage them [5].

Lastly, verify that all necessary services are running correctly by using the following commands:

docker compose ps

Ensure that the api, worker, web, weaviate, db, redis, and nginx services are all listed and in the Up status [6].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 28, 2024): <!-- Greeting --> Hello @PsycheJ! I'm here to help you with any bugs, questions, or contributions you may have for the repository. Let me know how I can assist you! <!-- Answer --> I found some similar issues and discussions that might help: 1. **Issue [#7675](https://github.com/langgenius/dify/issues/7675) (closed)**: The suggested solution was to check if the rate limit has been reached for the Embedding model API key used. Ensure the API key's rate limits are not exceeded, check for any constraints or limits, and verify that all necessary services, including the Celery worker service, are running correctly <sup>[[1]](https://github.com/langgenius/dify/issues/7675)</sup>. 2. **Issue [#7263](https://github.com/langgenius/dify/issues/7263) (closed)**: This issue was related to files being stuck in the "Queuing" status. The solution involved checking the rate limit for the Embedding model API key and ensuring the worker service is running correctly <sup>[[2]](https://github.com/langgenius/dify/issues/7263)</sup>. 3. **Discussion [#3283](https://github.com/langgenius/dify/discussions/3283)**: This discussion also addresses the issue of files being stuck in the queue and suggests similar solutions <sup>[[3]](https://github.com/langgenius/dify/discussions/3283)</sup>. For your specific case, ensure that the asynchronous queue worker is started by setting the `MODE` environment variable to `worker` in your Docker setup. Here is an example configuration for your Docker Compose file: ```yaml services: worker: image: your-docker-image environment: - MODE=worker ... ``` Without this configuration, the queue worker will not start, and the files will remain stuck in the queue <sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/environments.md)</sup>. Additionally, check the rate limits for the Embedding model API key and ensure they are not exceeded. You can refer to the [OpenAI official documentation](https://platform.openai.com/docs/guides/rate-limits) for details on rate limits and how to manage them <sup>[[5]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/faq/use-llms-faq.md)</sup>. Lastly, verify that all necessary services are running correctly by using the following commands: ```sh docker compose ps ``` Ensure that the `api`, `worker`, `web`, `weaviate`, `db`, `redis`, and `nginx` services are all listed and in the `Up` status <sup>[[6]](https://github.com/langgenius/dify/issues/6275)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:10:12 -05:00
Author
Owner
Copy Link
Copy Source

@CracKerMe commented on GitHub (Oct 12, 2024):

I encountered the same situation, but after I observed, the worker process in docker is abnormally occupied 100%, so it should be a bug in code execution.

Unfortunately, I ended up deleting the project and re-running it, so if you don't have any important information about your project, deleting the container, removing the cache, and storing irrelevant directories worked for me.

@CracKerMe commented on GitHub (Oct 12, 2024): I encountered the same situation, but after I observed, the worker process in docker is abnormally occupied 100%, so it should be a bug in code execution. Unfortunately, I ended up deleting the project and re-running it, so if you don't have any important information about your project, deleting the container, removing the cache, and storing irrelevant directories worked for me.
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#5271
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?