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

The Document Extractor tool encountered several abnormal situations #8461

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

Originally created by @yoke1990 on GitHub (Feb 20, 2025).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1.Upload docx，then Document Extractor report（Only a few docx documents will have errors）:
Failed to extract text from DOC/DOCX: "There is no item named 'NULL' in the archive"

Image

2.Upload file, the file content is too large, exceeding 80000 characters，Document Extractor report:

Image

3.Document Extractor tool exception occurred, there is no exception handling option, only error can be reported

4.Document Extractor tool extracts Excel content, but many NAN useless characters appear. Resulting in over 80000 characters.

It will extract both columns Excel and 255, such as "Unnamed: 253 | Unnamed: 254 | Unnamed: 255". In fact, most sequences are blank. So many 'nan | nan |'

So report “The length of output variable result must be less than 80000 characters”

5.Android phone on wechat, no file upload option

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @yoke1990 on GitHub (Feb 20, 2025). ### 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.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1.Upload docx，then Document Extractor report（Only a few docx documents will have errors）: Failed to extract text from DOC/DOCX: "There is no item named 'NULL' in the archive" <img width="471" alt="Image" src="https://github.com/user-attachments/assets/7e4d4e3c-b2d4-43f3-b83b-1874e1a38ca7" /> 2.Upload file, the file content is too large, exceeding 80000 characters，Document Extractor report: <img width="368" alt="Image" src="https://github.com/user-attachments/assets/87b8644e-5c67-4be4-bf78-abd54168122e" /> 3.Document Extractor tool exception occurred, there is no exception handling option, only error can be reported 4.Document Extractor tool extracts Excel content, but many NAN useless characters appear. Resulting in over 80000 characters. It will extract both columns Excel and 255, such as "Unnamed: 253 | Unnamed: 254 | Unnamed: 255". In fact, most sequences are blank. So many 'nan | nan |' So report “The length of output variable `result` must be less than 80000 characters” 5.Android phone on wechat, no file upload option <img width="398" alt="Image" src="https://github.com/user-attachments/assets/7b910455-0e4f-4cb7-ba01-7870124f43af" /> ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:25:48 -05:00
yindo closed this issue 2026-02-21 18:25:48 -05:00
yindo commented 2026-02-21 18:25:49 -05:00
Author
Owner
Copy Link
Copy Source

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

@yoke1990 Hello there! I'm here to help you with bug reports, answer questions, and even guide you on becoming a contributor. Let's squash those bugs together! 🤖

  1. DOCX Extraction Error: The error "There is no item named 'NULL' in the archive" suggests an issue with the DOCX file structure. This might be due to a corrupted file or an unsupported format. Ensure the DOCX files are not corrupted and are in a standard format.

  2. Character Limit Exceeded: The Document Extractor has a character limit of 80,000 for output variables. If the content exceeds this limit, consider splitting the document into smaller parts before processing or using the tool's chunking mechanism to handle large content [1].

  3. Exception Handling: The Document Extractor tool allows for customized error handling. You can specify a default value or a fail branch to handle exceptions without stopping the process [2].

  4. Excel NAN Values: The tool processes Excel files using pandas, which can result in 'nan' values for empty cells. To avoid this, ensure that the Excel files are cleaned of unnecessary empty columns before processing. The tool uses dropna to handle empty rows, but you might need to preprocess the file to remove empty columns [3].

  5. File Upload on Android/WeChat: There is no specific configuration mentioned for handling file uploads on mobile devices like Android or WeChat within the Dify platform. This might require additional customization or checking the mobile app's settings for file upload capabilities.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 20, 2025): <!-- Greeting --> @yoke1990 Hello there! I'm here to help you with bug reports, answer questions, and even guide you on becoming a contributor. Let's squash those bugs together! 🤖 <!-- Answer --> 1. **DOCX Extraction Error**: The error "There is no item named 'NULL' in the archive" suggests an issue with the DOCX file structure. This might be due to a corrupted file or an unsupported format. Ensure the DOCX files are not corrupted and are in a standard format. 2. **Character Limit Exceeded**: The Document Extractor has a character limit of 80,000 for output variables. If the content exceeds this limit, consider splitting the document into smaller parts before processing or using the tool's chunking mechanism to handle large content <sup>[[1]](https://github.com/langgenius/dify/blob/main/docker/docker-compose.yaml)</sup>. 3. **Exception Handling**: The Document Extractor tool allows for customized error handling. You can specify a default value or a fail branch to handle exceptions without stopping the process <sup>[[2]](https://github.com/langgenius/dify/blob/main/web/i18n/en-US/workflow.ts)</sup>. 4. **Excel NAN Values**: The tool processes Excel files using pandas, which can result in 'nan' values for empty cells. To avoid this, ensure that the Excel files are cleaned of unnecessary empty columns before processing. The tool uses `dropna` to handle empty rows, but you might need to preprocess the file to remove empty columns <sup>[[3]](https://github.com/langgenius/dify/blob/main/api/core/rag/extractor/excel_extractor.py)</sup>. 5. **File Upload on Android/WeChat**: There is no specific configuration mentioned for handling file uploads on mobile devices like Android or WeChat within the Dify platform. This might require additional customization or checking the mobile app's settings for file upload capabilities. <!-- 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/15fb93ab-2e6d-433f-b959-a32633c7792f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/15fb93ab-2e6d-433f-b959-a32633c7792f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/15fb93ab-2e6d-433f-b959-a32633c7792f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/15fb93ab-2e6d-433f-b959-a32633c7792f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/15fb93ab-2e6d-433f-b959-a32633c7792f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/15fb93ab-2e6d-433f-b959-a32633c7792f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/15fb93ab-2e6d-433f-b959-a32633c7792f?feedback_type=other)</sup>
yindo commented 2026-02-21 18:25:49 -05:00
Author
Owner
Copy Link
Copy Source

@yoke1990 commented on GitHub (Feb 20, 2025):

Both of these documents caused errors in the document extraction tool. You can test it

925523fea21073501b9765ffe0be96eb.docx

a6af9a7b61b8f03363aca1d45e378e23.xls

@yoke1990 commented on GitHub (Feb 20, 2025): Both of these documents caused errors in the document extraction tool. You can test it [925523fea21073501b9765ffe0be96eb.docx](https://github.com/user-attachments/files/18885136/925523fea21073501b9765ffe0be96eb.docx) [a6af9a7b61b8f03363aca1d45e378e23.xls](https://github.com/user-attachments/files/18885139/a6af9a7b61b8f03363aca1d45e378e23.xls)
yindo commented 2026-02-21 18:25:49 -05:00
Author
Owner
Copy Link
Copy Source

@yoke1990 commented on GitHub (Feb 20, 2025):

@dosu

hi.Thx for your reply

1.The docx file that causes errors can be edited and saved correctly by Word and WPS. The document written by the user using regular Office reports an error. I replied above the docx file, which can reproduce the error.

925523fea21073501b9765ffe0be96eb.docx

2 and 3.If the content exceeds 80000 character limit, The Document Extractor tool is not allows for customized error handling on v0.15.3

Image

4.It looks like it will force the reading of an Excel 255 line list. Generate a large number of empty columns

You can test it

a6af9a7b61b8f03363aca1d45e378e23.xls

5.With the same configuration, the option to upload documents can be displayed normally on iPhone. But Android phones don't work.

@yoke1990 commented on GitHub (Feb 20, 2025): @dosu hi.Thx for your reply 1.The docx file that causes errors can be edited and saved correctly by Word and WPS. The document written by the user using regular Office reports an error. I replied above the docx file, which can reproduce the error. [925523fea21073501b9765ffe0be96eb.docx](https://github.com/user-attachments/files/18885412/925523fea21073501b9765ffe0be96eb.docx) 2 and 3.If the content exceeds 80000 character limit, The Document Extractor tool is not allows for customized error handling on v0.15.3 <img width="329" alt="Image" src="https://github.com/user-attachments/assets/42404952-84e9-4bab-ab6b-d8e9368061fe" /> 4.It looks like it will force the reading of an Excel 255 line list. Generate a large number of empty columns You can test it [a6af9a7b61b8f03363aca1d45e378e23.xls](https://github.com/user-attachments/files/18885380/a6af9a7b61b8f03363aca1d45e378e23.xls) 5.With the same configuration, the option to upload documents can be displayed normally on iPhone. But Android phones don't work.
yindo commented 2026-02-21 18:25:49 -05:00
Author
Owner
Copy Link
Copy Source

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

  1. DOCX File Error: The error with the DOCX file might be due to specific content or structure that the Document Extractor tool cannot handle, even if it appears fine in Word or WPS. The _extract_text_from_docx function in the code handles DOCX extraction and raises a TextExtractionError if it encounters issues [1]. You might need to inspect the file's content or structure for anomalies that could cause this error.

  2. Character Limit Handling: In version 0.15.3, the Document Extractor tool enforces a character limit of 80,000, and it seems there is no built-in mechanism for customized error handling when this limit is exceeded. You may need to manually split the content into smaller parts before processing.

  3. Excel File Empty Columns: The tool processes Excel files using pandas, and it drops rows where all elements are NaN using df.dropna(how="all", inplace=True). However, it seems to read all columns, including empty ones, which might result in unnecessary 'nan' values. Preprocessing the Excel file to remove empty columns before using the tool could help [1][2].

  4. File Upload on Android: The issue with file uploads on Android but not on iPhone might be related to platform-specific configurations or limitations. Unfortunately, there is no specific documentation or code in the repository addressing this difference. You might need to explore the mobile app's settings or configurations for file uploads.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 20, 2025): <!-- Answer --> 1. **DOCX File Error**: The error with the DOCX file might be due to specific content or structure that the Document Extractor tool cannot handle, even if it appears fine in Word or WPS. The `_extract_text_from_docx` function in the code handles DOCX extraction and raises a `TextExtractionError` if it encounters issues <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/workflow/nodes/document_extractor/node.py)</sup>. You might need to inspect the file's content or structure for anomalies that could cause this error. 2. **Character Limit Handling**: In version 0.15.3, the Document Extractor tool enforces a character limit of 80,000, and it seems there is no built-in mechanism for customized error handling when this limit is exceeded. You may need to manually split the content into smaller parts before processing. 3. **Excel File Empty Columns**: The tool processes Excel files using pandas, and it drops rows where all elements are `NaN` using `df.dropna(how="all", inplace=True)`. However, it seems to read all columns, including empty ones, which might result in unnecessary 'nan' values. Preprocessing the Excel file to remove empty columns before using the tool could help <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/workflow/nodes/document_extractor/node.py)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/rag/extractor/excel_extractor.py)</sup>. 4. **File Upload on Android**: The issue with file uploads on Android but not on iPhone might be related to platform-specific configurations or limitations. Unfortunately, there is no specific documentation or code in the repository addressing this difference. You might need to explore the mobile app's settings or configurations for file uploads. <!-- 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/6e7a8db4-b78d-419f-8663-19e625ea257d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/6e7a8db4-b78d-419f-8663-19e625ea257d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/6e7a8db4-b78d-419f-8663-19e625ea257d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/6e7a8db4-b78d-419f-8663-19e625ea257d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6e7a8db4-b78d-419f-8663-19e625ea257d?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/6e7a8db4-b78d-419f-8663-19e625ea257d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6e7a8db4-b78d-419f-8663-19e625ea257d?feedback_type=other)</sup>
yindo commented 2026-02-21 18:25:49 -05:00
Author
Owner
Copy Link
Copy Source

@yoke1990 commented on GitHub (Feb 20, 2025):

  1. I also know that it's difficult to be compatible with different document formats, so I will come up with a solution myself, such as writing a tool to convert to a standard format.

Of course, I would prefer Dify to improve compatibility with office documents

  1. I hope that future versions will add exception handling options to the document extraction tool
@yoke1990 commented on GitHub (Feb 20, 2025): 1. I also know that it's difficult to be compatible with different document formats, so I will come up with a solution myself, such as writing a tool to convert to a standard format. Of course, I would prefer Dify to improve compatibility with office documents 2. I hope that future versions will add exception handling options to the document extraction tool
yindo commented 2026-02-21 18:25:49 -05:00
Author
Owner
Copy Link
Copy Source

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

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

Issue Summary

  • Reported issues with Document Extractor in Dify v0.15.3, including errors with DOCX files and large file handling.
  • Problems with exception handling and 'nan' character extraction from Excel files.
  • File upload issues on Android devices using WeChat.
  • I suggested checking file integrity and preprocessing Excel files as workarounds.
  • You acknowledged the need for improved document compatibility and exception handling.

Next Steps

  • Please confirm if this issue is still relevant to 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 23, 2025): Hi, @yoke1990. 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** - Reported issues with Document Extractor in Dify v0.15.3, including errors with DOCX files and large file handling. - Problems with exception handling and 'nan' character extraction from Excel files. - File upload issues on Android devices using WeChat. - I suggested checking file integrity and preprocessing Excel files as workarounds. - You acknowledged the need for improved document compatibility and exception handling. **Next Steps** - Please confirm if this issue is still relevant to 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 🐞 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#8461
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?