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

Dify - Knowledge Base - Status Queuing #5226

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

Originally created by @PubliBrasil on GitHub (Aug 26, 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.7.1

Cloud or Self Hosted

Cloud

Steps to reproduce

I started to encounter problems when uploading any file to the knowledge base to Cloud Dify, manually or via API.
Captura de Tela 2024-08-26 às 15 39 29
I checked and found no limitations on the account.
Captura de Tela 2024-08-26 às 15 41 06

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @PubliBrasil on GitHub (Aug 26, 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.7.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce I started to encounter problems when uploading any file to the knowledge base to Cloud Dify, manually or via API. ![Captura de Tela 2024-08-26 às 15 39 29](https://github.com/user-attachments/assets/64a50b61-88e4-4285-a698-95fb61bad554) I checked and found no limitations on the account. ![Captura de Tela 2024-08-26 às 15 41 06](https://github.com/user-attachments/assets/4705ca5c-2af1-4bb4-9821-6dc4adae6f12) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:09:57 -05:00
yindo closed this issue 2026-02-21 18:09:57 -05:00
yindo commented 2026-02-21 18:09:57 -05:00
Author
Owner
Copy Link
Copy Source

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

Hello, @PubliBrasil! I'm here to assist you with any bugs, questions, or contributions regarding Dify's Knowledge Base. Let's take a look at the issue you've encountered.

I found similar issues and discussions related to files being stuck in the "Queuing" status when uploading to the knowledge base in Dify:

  1. Issue #7263 (closed): The suggested solution was to check if the rate limit has been reached for the Embedding model API key used.
  2. Issue #5184 (closed): The solution involved checking document limits, subscription constraints, and ensuring the worker service is running correctly.
  3. Issue #696 (closed): The problem was related to insufficient OpenAI API key quotas, causing constant retries and blocking queue consumption.

For your specific case in Cloud Dify, the most likely cause is that the rate limit has been reached for the Embedding model API key used [1].

To resolve this, you should:

  1. Verify the API key's rate limits and ensure they are not exceeded.
  2. Check if there are any other constraints or limits being hit, such as document limits or subscription constraints.
  3. Ensure that all necessary services, including the Celery worker service, are running correctly.

If the issue persists, you may need to review the logs for any errors or warnings that could provide more insight into why the files are stuck in the "Queuing" status.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 26, 2024): <!-- Greeting --> Hello, @PubliBrasil! I'm here to assist you with any bugs, questions, or contributions regarding Dify's Knowledge Base. Let's take a look at the issue you've encountered. <!-- Answer --> I found similar issues and discussions related to files being stuck in the "Queuing" status when uploading to the knowledge base in Dify: 1. **Issue [#7263](https://github.com/langgenius/dify/issues/7263)** (closed): The suggested solution was to check if the rate limit has been reached for the Embedding model API key used. 2. **Issue [#5184](https://github.com/langgenius/dify/issues/5184)** (closed): The solution involved checking document limits, subscription constraints, and ensuring the worker service is running correctly. 3. **Issue [#696](https://github.com/langgenius/dify/issues/696)** (closed): The problem was related to insufficient OpenAI API key quotas, causing constant retries and blocking queue consumption. For your specific case in Cloud Dify, the most likely cause is that the rate limit has been reached for the Embedding model API key used <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/application-orchestrate/llms-use-faq.md)</sup>. To resolve this, you should: 1. Verify the API key's rate limits and ensure they are not exceeded. 2. Check if there are any other constraints or limits being hit, such as document limits or subscription constraints. 3. Ensure that all necessary services, including the Celery worker service, are running correctly. If the issue persists, you may need to review the logs for any errors or warnings that could provide more insight into why the files are stuck in the "Queuing" status. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:09:57 -05:00
Author
Owner
Copy Link
Copy Source

@PubliBrasil commented on GitHub (Aug 26, 2024):

@dosu I have already checked Dify's limits, as shown in the image I sent previously, and they were not reached.
I analyzed the Embedding Model API - Cohere - which is paid - I also did not reach the limit.

@PubliBrasil commented on GitHub (Aug 26, 2024): @dosu I have already checked Dify's limits, as shown in the image I sent previously, and they were not reached. I analyzed the Embedding Model API - Cohere - which is paid - I also did not reach the limit.
yindo commented 2026-02-21 18:09:57 -05:00
Author
Owner
Copy Link
Copy Source

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

If you've confirmed that neither Dify's limits nor the Embedding Model API limits have been reached, there are a few other potential causes to investigate:

  1. Check for Specific Error Messages or Logs:
    Review the logs for any specific error messages that might indicate the cause of the issue. Common error messages include:

    • provider_not_initialize: Embedding model not configured
    • provider_quota_exceeded: Model quota exceeded
    • unsupported_file_type: Unsupported file type
    • too_many_files: Too many files
    • file_too_large: File too large
    • document_indexing: Document indexing failed
    • not_found: Document not found
    • dataset_name_duplicate: Dataset name duplicate
    • dataset_not_initialized: Dataset not initialized [1][2].

  2. Verify Celery Worker Service:
    Ensure that the Celery worker service is running correctly. This service is responsible for processing tasks such as document indexing. You can verify and troubleshoot the Celery worker service by following these steps:

    • Start the Celery worker service with the appropriate command for your system.
    • Check the logs for any errors or warnings.
    • Ensure all dependencies are correctly installed.
    • Verify that the .env file is correctly configured.
    • Ensure that the database is migrated to the latest version.
    • Verify that all required middleware services (PostgreSQL, Redis, Weaviate) are running [3][4].

  3. Logs and Debugging Tools:
    Utilize Dify's Logs feature to diagnose issues with document uploads. This feature allows you to observe and mark the interactions of the Dify app, providing insights into user inputs, AI outputs, and evaluations by users and operators [5].

By following these steps, you should be able to identify and resolve the issue causing your files to be stuck in the "Queuing" status.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Aug 26, 2024): <!-- Answer --> If you've confirmed that neither Dify's limits nor the Embedding Model API limits have been reached, there are a few other potential causes to investigate: 1. **Check for Specific Error Messages or Logs:** Review the logs for any specific error messages that might indicate the cause of the issue. Common error messages include: - `provider_not_initialize`: Embedding model not configured - `provider_quota_exceeded`: Model quota exceeded - `unsupported_file_type`: Unsupported file type - `too_many_files`: Too many files - `file_too_large`: File too large - `document_indexing`: Document indexing failed - `not_found`: Document not found - `dataset_name_duplicate`: Dataset name duplicate - `dataset_not_initialized`: Dataset not initialized <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/application-orchestrate/llms-use-faq.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/guides/knowledge-base/maintain-dataset-via-api.md)</sup>. 2. **Verify Celery Worker Service:** Ensure that the Celery worker service is running correctly. This service is responsible for processing tasks such as document indexing. You can verify and troubleshoot the Celery worker service by following these steps: - Start the Celery worker service with the appropriate command for your system. - Check the logs for any errors or warnings. - Ensure all dependencies are correctly installed. - Verify that the `.env` file is correctly configured. - Ensure that the database is migrated to the latest version. - Verify that all required middleware services (PostgreSQL, Redis, Weaviate) are running <sup>[[3]](https://github.com/langgenius/dify/blob/main/api/README.md)</sup><sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/local-source-code.md)</sup>. 3. **Logs and Debugging Tools:** Utilize Dify's Logs feature to diagnose issues with document uploads. This feature allows you to observe and mark the interactions of the Dify app, providing insights into user inputs, AI outputs, and evaluations by users and operators <sup>[[5]](https://github.com/langgenius/dify-docs/blob/main/jp/guides/biao-zhu/logs.md)</sup>. By following these steps, you should be able to identify and resolve the issue causing your files to be stuck in the "Queuing" status. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:09:57 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 26, 2024):

We are currently working on it

@crazywoola commented on GitHub (Aug 26, 2024): We are currently working on it
yindo commented 2026-02-21 18:09:58 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 26, 2024):

It's resolved now.

@crazywoola commented on GitHub (Aug 26, 2024): It's resolved now.
yindo commented 2026-02-21 18:09:58 -05:00
Author
Owner
Copy Link
Copy Source

@AoChem commented on GitHub (Nov 19, 2025):

Image Is this issue coming again? I changed the embedding model and still it's in queuing...
@AoChem commented on GitHub (Nov 19, 2025): <img width="331" height="299" alt="Image" src="https://github.com/user-attachments/assets/63f46a10-8ae3-4af4-91ec-97435bd92f8e" /> Is this issue coming again? I changed the embedding model and still it's in queuing...
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#5226
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?