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

upload document #6688

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

Originally created by @af-74413592 on GitHub (Nov 11, 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.11.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

image
上传之后一直显示解析0%，只有一个文件，排队中，pdf和txt都测试过了。

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @af-74413592 on GitHub (Nov 11, 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.11.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![image](https://github.com/user-attachments/assets/a820ae27-e890-4daa-9f3a-61ccdf53d8be) 上传之后一直显示解析0%，只有一个文件，排队中，pdf和txt都测试过了。 ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-21 18:16:51 -05:00
yindo commented 2026-02-21 18:16:52 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 11, 2024):

Hello @af-74413592! I'm here to help you with any bugs, questions, or contributions you may have. Let's work together to solve the issue you're experiencing.

I found some similar issues and discussions that might help you with the problem of uploaded documents staying at 0% parsing:

  1. Knowledgebase upload file stay in Queue: This issue was closed, and the suggested solutions included checking for pending segmentation or embedding processes, ensuring there are no resource limitations, and verifying configuration settings. Additionally, make sure all dependencies and services like db and redis are running smoothly, and check server logs for any errors. Also, verify if the Celery worker has been started [1].

  2. Dify - Knowledge Base - Status Queuing: This closed issue suggested verifying API key rate limits, checking for any constraints or limits, ensuring all necessary services are running, and reviewing logs for specific error messages. Utilizing Dify's Logs feature can also help diagnose issues with document uploads [2].

  3. Knowledge base problem: Uploaded files are queued: To resolve this, it was recommended to sync the environment variable configuration by updating your local .env file to match any new variables or changes in the .env.example file. Also, ensure that encryption keys are correctly set up, as missing or incorrect keys can cause issues with file processing [3].

These solutions might help you troubleshoot and resolve the issue with your document uploads.

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Nov 11, 2024): <!-- Greeting --> Hello @af-74413592! I'm here to help you with any bugs, questions, or contributions you may have. Let's work together to solve the issue you're experiencing. <!-- Answer --> I found some similar issues and discussions that might help you with the problem of uploaded documents staying at 0% parsing: 1. **[Knowledgebase upload file stay in Queue](https://github.com/langgenius/dify/issues/9043)**: This issue was closed, and the suggested solutions included checking for pending segmentation or embedding processes, ensuring there are no resource limitations, and verifying configuration settings. Additionally, make sure all dependencies and services like `db` and `redis` are running smoothly, and check server logs for any errors. Also, verify if the Celery worker has been started <sup>[[1]](https://github.com/langgenius/dify/issues/9043)</sup>. 2. **[Dify - Knowledge Base - Status Queuing](https://github.com/langgenius/dify/issues/7675)**: This closed issue suggested verifying API key rate limits, checking for any constraints or limits, ensuring all necessary services are running, and reviewing logs for specific error messages. Utilizing Dify's Logs feature can also help diagnose issues with document uploads <sup>[[2]](https://github.com/langgenius/dify/issues/7675)</sup>. 3. **[Knowledge base problem: Uploaded files are queued](https://github.com/langgenius/dify/issues/8525)**: To resolve this, it was recommended to sync the environment variable configuration by updating your local `.env` file to match any new variables or changes in the `.env.example` file. Also, ensure that encryption keys are correctly set up, as missing or incorrect keys can cause issues with file processing <sup>[[3]](https://github.com/langgenius/dify/issues/8525)</sup>. These solutions might help you troubleshoot and resolve the issue with your document uploads. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:16:52 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 11, 2024):

  • All descriptions should be English
  • Please provide the container logs, an image isn't enough to investigate the issue.
@crazywoola commented on GitHub (Nov 11, 2024): - All descriptions should be English - Please provide the container logs, an image isn't enough to investigate the issue.
yindo commented 2026-02-21 18:16:52 -05:00
Author
Owner
Copy Link
Copy Source

@sweetkey commented on GitHub (Nov 12, 2024):

Same thing here, After upgraded to 0.11.1, new uploaded files stay at the status of Queuing.

By the way, where to find the log file?

@sweetkey commented on GitHub (Nov 12, 2024): Same thing here, After upgraded to 0.11.1, new uploaded files stay at the status of Queuing. By the way, where to find the log file?
yindo commented 2026-02-21 18:16:52 -05:00
Author
Owner
Copy Link
Copy Source

@RollingDonkeyX commented on GitHub (Nov 12, 2024):

Same thing here, After upgraded to 0.11.1,

@RollingDonkeyX commented on GitHub (Nov 12, 2024): Same thing here, After upgraded to 0.11.1,
yindo commented 2026-02-21 18:16:52 -05:00
Author
Owner
Copy Link
Copy Source

@negative-crush commented on GitHub (Nov 13, 2024):

Same thing here, After upgraded to 0.11.1,
微信截图_20241113193446

@negative-crush commented on GitHub (Nov 13, 2024): Same thing here, After upgraded to 0.11.1, ![微信截图_20241113193446](https://github.com/user-attachments/assets/4d0de012-5b40-4f74-be66-7ac93fc3dd4d)
yindo commented 2026-02-21 18:16:52 -05:00
Author
Owner
Copy Link
Copy Source

@negative-crush commented on GitHub (Nov 13, 2024):

image

@negative-crush commented on GitHub (Nov 13, 2024): ![image](https://github.com/user-attachments/assets/c15f2040-0301-49e3-9f1a-7f20e67aceaf)
yindo commented 2026-02-21 18:16:52 -05:00
Author
Owner
Copy Link
Copy Source

@Kevinhuhu commented on GitHub (Nov 14, 2024):

Same thing here, After upgraded to 0.11.1
QQ_1731608406638

@Kevinhuhu commented on GitHub (Nov 14, 2024): Same thing here, After upgraded to 0.11.1 ![QQ_1731608406638](https://github.com/user-attachments/assets/6b1259c4-b0ba-438d-8626-05fd3f935640)
yindo commented 2026-02-21 18:16:52 -05:00
Author
Owner
Copy Link
Copy Source

@burnedsyn commented on GitHub (Nov 18, 2024):

Same thing here, After upgraded to 0.11.1 QQ_1731608406638

i had the same thing with 0.11.1 just upgraded to 0.11.2 and it work fine

@burnedsyn commented on GitHub (Nov 18, 2024): > Same thing here, After upgraded to 0.11.1 ![QQ_1731608406638](https://private-user-images.githubusercontent.com/7582366/386321899-6b1259c4-b0ba-438d-8626-05fd3f935640.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzE5NDQ4MDIsIm5iZiI6MTczMTk0NDUwMiwicGF0aCI6Ii83NTgyMzY2LzM4NjMyMTg5OS02YjEyNTljNC1iMGJhLTQzOGQtODYyNi0wNWZkM2Y5MzU2NDAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MTExOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDExMThUMTU0MTQyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9Y2NmNDMxMTcyODMzNWFiNWQxNmVmYzc2ZDY5MjA2MDM3MjNjMWQyNmU0MzdiYTY0MDllM2MzZDZjMjhkMDY3OSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.4XxywwQtM759Phqq4tMe1QawKFPFc8v_rJQ0DTrJaxE) i had the same thing with 0.11.1 just upgraded to 0.11.2 and it work fine
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#6688
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?