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

While passing files in document extractor, sometime it take's files (size is not the concern, I've updated env and uploading perfectly) and sometime it does not, it just throws empty string, how to resolve it? #20567

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

Originally created by @raj-triforce on GitHub (Nov 26, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Connect the document extractor node with starting node and just try to get the output with some file's its working fine as expected but many time it's causing the issue it not taking it.

we can see in actual behaviour it is pass null id. it is happing only with some document if i pass any other sometimes it work and other time it just give me these kind of output which is just empty string.

{
"text": ""
}

✔️ Expected Behavior

It should extract textual content from the pdf or docx and forward that to next node.

❌ Actual Behavior

{
"documents": [
{
"dify_model_identity": "dify__file",
"extension": ".pdf",
"filename": "Enclosure 5 - eCMMS Assessment.1764013032480.pdf",
"id": null,
"mime_type": "application/pdf",
"related_id": "bbd90178-ecd4-468a-8233-6dc5b2091934",
"remote_url": "/files/bbd90178-ecd4-468a-8233-6dc5b2091934/file-preview?timestamp=1764141380&nonce=449a3923d8668cbb4123f57b113da15e&sign=zToNp6xWMY2sDxqSoP3E4r8Ja9zLsl-wzbGOHmBagxY%3D",
"size": 38478561,
"tenant_id": "b34f2a30-49fb-45a2-a1ca-966328cc0d99",
"transfer_method": "local_file",
"type": "document",
"url": "/files/bbd90178-ecd4-468a-8233-6dc5b2091934/file-preview?timestamp=1764146617&nonce=cdba9458608334e3ded0ab1c5caaba7b&sign=dSSY4vJ5esczNgXqjgBWBmWLPu2fb0_KA3AKoKaMoOI%3D"
}
]
}

Originally created by @raj-triforce on GitHub (Nov 26, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Connect the document extractor node with starting node and just try to get the output with some file's its working fine as expected but many time it's causing the issue it not taking it. we can see in actual behaviour it is pass null id. it is happing only with some document if i pass any other sometimes it work and other time it just give me these kind of output which is just empty string. { "text": "" } ### ✔️ Expected Behavior It should extract textual content from the pdf or docx and forward that to next node. ### ❌ Actual Behavior { "documents": [ { "dify_model_identity": "__dify__file__", "extension": ".pdf", "filename": "Enclosure 5 - eCMMS Assessment.1764013032480.pdf", "id": null, "mime_type": "application/pdf", "related_id": "bbd90178-ecd4-468a-8233-6dc5b2091934", "remote_url": "/files/bbd90178-ecd4-468a-8233-6dc5b2091934/file-preview?timestamp=1764141380&nonce=449a3923d8668cbb4123f57b113da15e&sign=zToNp6xWMY2sDxqSoP3E4r8Ja9zLsl-wzbGOHmBagxY%3D", "size": 38478561, "tenant_id": "b34f2a30-49fb-45a2-a1ca-966328cc0d99", "transfer_method": "local_file", "type": "document", "url": "/files/bbd90178-ecd4-468a-8233-6dc5b2091934/file-preview?timestamp=1764146617&nonce=cdba9458608334e3ded0ab1c5caaba7b&sign=dSSY4vJ5esczNgXqjgBWBmWLPu2fb0_KA3AKoKaMoOI%3D" } ] }
yindo added the 🐞 bug label 2026-02-21 20:07:59 -05:00
yindo closed this issue 2026-02-21 20:07:59 -05:00
yindo commented 2026-02-21 20:07:59 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 26, 2025):

Hi @raj-triforce! I'm Dosu and I’m helping the dify team.

This issue is often caused by the document extractor node not receiving the actual file content (the "blob")—even if the metadata and remote URL are present, extraction will silently fail and return empty output fields if the file bytes are missing. This can happen intermittently if the workflow variable propagation is inconsistent, or if there are memory/resource constraints in your Docker setup that prevent files from being loaded into memory as expected. It can also occur if the node is referencing the wrong variable or if the frontend variable picker filters out the output due to schema mismatches [source 1] [source 2] [source 3].

To resolve this:

  • Check that the file content is present in the workflow variable at the point where the extractor runs (not just the metadata or URL).
  • Make sure your Docker containers have enough memory and CPU allocated, as files are processed in-memory.
  • Inspect your workflow to ensure the correct file variable is being passed to the extractor node each time.
  • Monitor logs for any resource or download errors.
  • If you use plugins or custom integrations, ensure they are up to date and that they pass the file bytes, not just references.

Testing with a minimal workflow and a known-good file can help isolate whether the problem is with specific documents or with the workflow/environment setup.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 26, 2025): <!-- Greeting --> Hi @raj-triforce! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This issue is often caused by the document extractor node not receiving the actual file content (the "blob")—even if the metadata and remote URL are present, extraction will silently fail and return empty output fields if the file bytes are missing. This can happen intermittently if the workflow variable propagation is inconsistent, or if there are memory/resource constraints in your Docker setup that prevent files from being loaded into memory as expected. It can also occur if the node is referencing the wrong variable or if the frontend variable picker filters out the output due to schema mismatches [[source 1]](https://github.com/langgenius/dify-official-plugins/issues/1857) [[source 2]](https://github.com/langgenius/dify-official-plugins/issues/1311) [[source 3]](https://github.com/langgenius/dify-official-plugins/issues/2074). To resolve this: - Check that the file content is present in the workflow variable at the point where the extractor runs (not just the metadata or URL). - Make sure your Docker containers have enough memory and CPU allocated, as files are processed in-memory. - Inspect your workflow to ensure the correct file variable is being passed to the extractor node each time. - Monitor logs for any resource or download errors. - If you use plugins or custom integrations, ensure they are up to date and that they pass the file bytes, not just references. Testing with a minimal workflow and a known-good file can help isolate whether the problem is with specific documents or with the workflow/environment setup. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/a4d39f2a-7942-4902-8d26-67eb7d5eb169?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a4d39f2a-7942-4902-8d26-67eb7d5eb169?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a4d39f2a-7942-4902-8d26-67eb7d5eb169?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a4d39f2a-7942-4902-8d26-67eb7d5eb169?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a4d39f2a-7942-4902-8d26-67eb7d5eb169?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a4d39f2a-7942-4902-8d26-67eb7d5eb169?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a4d39f2a-7942-4902-8d26-67eb7d5eb169?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20issue%20is%20often%20caused%20by%20the%20document%20extractor%20node%20not%20receiving%20the%20actual%20file%20content%20%28the%20%22blob%22%29%E2%80%94even%20if%20the%20metadata%20and%20remote%20URL%20are%20present%2C%20extraction%20will%20silently%20fail%20and%20return%20empty%20output%20fields%20if%20the%20file%20bytes%20are%20missing.%20This%20can%20happen%20intermittently%20if%20the%20workflow%20variable%20propagation%20is%20inconsistent%2C%20or%20if%20there%20are%20memory/resource%20constraints%20in%20your%20Docker%20setup%20that%20prevent%20files%20from%20being%20loaded%20into%20memory%20as%20expected.%20It%20can%20also%20occur%20if%20the%20node%20is%20referencing%20the%20wrong%20variable%20or%20if%20the%20frontend%20variable%20picker%20filters%20out%20the%20output%20due%20to%20schema%20mismatches%20%5B%5Bsource%201%5D%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1857%29%20%5B%5Bsource%202%5D%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/1311%29%20%5B%5Bsource%203%5D%5D%28https%3A//github.com/langgenius/dify-official-plugins/issues/2074%29.%0A%0ATo%20resolve%20this%3A%0A-%20Check%20that%20the%20file%20content%20is%20present%20in%20the%20workflow%20variable%20at%20the%20point%20where%20the%20extractor%20runs%20%28not%20just%20the%20metadata%20or%20URL%29.%0A-%20Make%20sure%20your%20Docker%20containers%20have%20enough%20memory%20and%20CPU%20allocated%2C%20as%20files%20are%20processed%20in-memory.%0A-%20Inspect%20your%20workflow%20to%20ensure%20the%20correct%20file%20variable%20is%20being%20passed%20to%20the%20extractor%20node%20each%20time.%0A-%20Monitor%20logs%20for%20any%20resource%20or%20download%20errors.%0A-%20If%20you%20use%20plugins%20or%20custom%20integrations%2C%20ensure%20they%20are%20up%20to%20date%20and%20that%20they%20pass%20the%20file%20bytes%2C%20not%20just%20references.%0A%0ATesting%20with%20a%20minimal%20workflow%20and%20a%20known-good%20file%20can%20help%20isolate%20whether%20the%20problem%20is%20with%20specific%20documents%20or%20with%20the%20workflow/environment%20setup.)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28693)
yindo commented 2026-02-21 20:07:59 -05:00
Author
Owner
Copy Link
Copy Source

@raj-triforce commented on GitHub (Nov 26, 2025):

@dosu. okay I've tried it, even file's which were getting upload earlier are throwing error's if you need more particular debug info about anything, let me know.

@raj-triforce commented on GitHub (Nov 26, 2025): @dosu. okay I've tried it, even file's which were getting upload earlier are throwing error's if you need more particular debug info about anything, let me know.
yindo commented 2026-02-21 20:07:59 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 26, 2025):

To help diagnose this, could you share the exact error messages or stack traces from your Docker logs (API and worker containers) when extraction fails—especially for files that used to work? Also, if you can, please provide details about your workflow setup: how file variables are mapped to the document extractor node, and whether you’ve changed anything recently.

It would also help to know if the issue happens with both PDF and DOCX files, and if you notice any patterns (file type, encoding, etc.) among the failing files. If you have a sample file that consistently fails (and it’s safe to share), or if the problem happens even with a minimal workflow and a known-good file, that info would be useful.

Finally, double-check that your .env file has FILES_URL and INTERNAL_FILES_URL set correctly, and that Docker is exposing port 5001 as required—misconfigurations here can cause extraction failures even if uploads succeed (reference). If you need instructions for enabling debug logging, let me know!

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 26, 2025): <!-- Answer --> To help diagnose this, could you share the exact error messages or stack traces from your Docker logs (API and worker containers) when extraction fails—especially for files that used to work? Also, if you can, please provide details about your workflow setup: how file variables are mapped to the document extractor node, and whether you’ve changed anything recently. It would also help to know if the issue happens with both PDF and DOCX files, and if you notice any patterns (file type, encoding, etc.) among the failing files. If you have a sample file that consistently fails (and it’s safe to share), or if the problem happens even with a minimal workflow and a known-good file, that info would be useful. Finally, double-check that your .env file has FILES_URL and INTERNAL_FILES_URL set correctly, and that Docker is exposing port 5001 as required—misconfigurations here can cause extraction failures even if uploads succeed ([reference](https://github.com/langgenius/dify/blob/ef0e1031b04f167e93344d848273b96b8daac64d/docker/.env.example#L47-L149)). If you need instructions for enabling debug logging, let me know! <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/0a82e489-3690-4d13-a91e-7867a97cef77?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/0a82e489-3690-4d13-a91e-7867a97cef77?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/0a82e489-3690-4d13-a91e-7867a97cef77?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/0a82e489-3690-4d13-a91e-7867a97cef77?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0a82e489-3690-4d13-a91e-7867a97cef77?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/0a82e489-3690-4d13-a91e-7867a97cef77?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0a82e489-3690-4d13-a91e-7867a97cef77?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=To%20help%20diagnose%20this%2C%20could%20you%20share%20the%20exact%20error%20messages%20or%20stack%20traces%20from%20your%20Docker%20logs%20%28API%20and%20worker%20containers%29%20when%20extraction%20fails%E2%80%94especially%20for%20files%20that%20used%20to%20work%3F%20Also%2C%20if%20you%20can%2C%20please%20provide%20details%20about%20your%20workflow%20setup%3A%20how%20file%20variables%20are%20mapped%20to%20the%20document%20extractor%20node%2C%20and%20whether%20you%E2%80%99ve%20changed%20anything%20recently.%0A%0AIt%20would%20also%20help%20to%20know%20if%20the%20issue%20happens%20with%20both%20PDF%20and%20DOCX%20files%2C%20and%20if%20you%20notice%20any%20patterns%20%28file%20type%2C%20encoding%2C%20etc.%29%20among%20the%20failing%20files.%20If%20you%20have%20a%20sample%20file%20that%20consistently%20fails%20%28and%20it%E2%80%99s%20safe%20to%20share%29%2C%20or%20if%20the%20problem%20happens%20even%20with%20a%20minimal%20workflow%20and%20a%20known-good%20file%2C%20that%20info%20would%20be%20useful.%0A%0AFinally%2C%20double-check%20that%20your%20.env%20file%20has%20FILES_URL%20and%20INTERNAL_FILES_URL%20set%20correctly%2C%20and%20that%20Docker%20is%20exposing%20port%205001%20as%20required%E2%80%94misconfigurations%20here%20can%20cause%20extraction%20failures%20even%20if%20uploads%20succeed%20%28%5Breference%5D%28https%3A//github.com/langgenius/dify/blob/ef0e1031b04f167e93344d848273b96b8daac64d/docker/.env.example%23L47-L149%29%29.%20If%20you%20need%20instructions%20for%20enabling%20debug%20logging%2C%20let%20me%20know%21)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28693)
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#20567
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?