langgenius/dify-official-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-official-plugins.git synced 2026-07-21 17:45:23 -04:00
Code Issues 54 Packages Projects Releases Wiki Activity

LLM can't get document when using qwen-long #413

New Issue
Closed
opened 2026-02-16 10:19:21 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 10:19:21 -05:00
Owner
Copy Link
Copy Source

Originally created by @camer100 on GitHub (Jul 1, 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

1.5.0

Cloud or Self Hosted

Cloud

Steps to reproduce

  1. using qwen-long LLM
  2. upload a word file
  3. ask LLM some question
  4. LLM tell me no word file found

✔️ Expected Behavior

Image when use office website, the LLM worked Image

❌ Actual Behavior

Image
Originally created by @camer100 on GitHub (Jul 1, 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 1.5.0 ### Cloud or Self Hosted Cloud ### Steps to reproduce 1. using qwen-long LLM 2. upload a word file 3. ask LLM some question 4. LLM tell me no word file found ### ✔️ Expected Behavior <img width="735" alt="Image" src="https://github.com/user-attachments/assets/7aa50020-4709-4606-b2b7-6f163a587e03" /> when use office website, the LLM worked <img width="1315" alt="Image" src="https://github.com/user-attachments/assets/09651810-1ce2-48d1-927a-730659d571df" /> ### ❌ Actual Behavior <img width="727" alt="Image" src="https://github.com/user-attachments/assets/664d9c0e-23e6-4683-9733-a728d0832f4a" />
yindo closed this issue 2026-02-16 10:19:21 -05:00
yindo commented 2026-02-16 10:19:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 1, 2025):

Hi @camer100! I'm Dosu and I’m helping the dify team.

This is a known limitation in Dify: LLM nodes (including qwen-long) can't process Word (DOCX) files directly. To make this work, you need to add a Document Extractor node to your workflow. The Document Extractor converts the DOCX file to text, and you then connect its output (usually called text) to the LLM node's prompt. Without this step, the LLM will always say "no word file found" because it only receives text, not raw files. This is required for all LLMs in Dify, not just qwen-long, even if the LLM itself supports direct document input on other platforms. For setup details, see the file upload guide and Document Extractor node docs
(source).

The "office website" you mentioned likely supports direct DOCX input, but Dify currently does not—this workflow step is required.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 1, 2025): <!-- Greeting --> Hi @camer100! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This is a known limitation in Dify: LLM nodes (including qwen-long) can't process Word (DOCX) files directly. To make this work, you need to add a Document Extractor node to your workflow. The Document Extractor converts the DOCX file to text, and you then connect its output (usually called `text`) to the LLM node's prompt. Without this step, the LLM will always say "no word file found" because it only receives text, not raw files. This is required for all LLMs in Dify, not just qwen-long, even if the LLM itself supports direct document input on other platforms. For setup details, see the [file upload guide](https://github.com/crazywoola/dify-docs-mintlify/blob/766ba4baea07dd783e72dcc745d2a4cffd03d2e8/en/guides/workflow/file-upload.mdx) and [Document Extractor node docs](https://github.com/crazywoola/dify-docs-mintlify/blob/766ba4baea07dd783e72dcc745d2a4cffd03d2e8/en/guides/workflow/node/doc-extractor.mdx) ([source](https://github.com/langgenius/dify/issues/21375)). The "office website" you mentioned likely supports direct DOCX input, but Dify currently does not—this workflow step is required. <!-- 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/ae7be128-a1a5-4e8c-a055-094007069d7e?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ae7be128-a1a5-4e8c-a055-094007069d7e?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ae7be128-a1a5-4e8c-a055-094007069d7e?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ae7be128-a1a5-4e8c-a055-094007069d7e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ae7be128-a1a5-4e8c-a055-094007069d7e?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ae7be128-a1a5-4e8c-a055-094007069d7e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ae7be128-a1a5-4e8c-a055-094007069d7e?feedback_type=other)</sup>&nbsp;&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/21775)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
bug
dependencies
documentation
enhancement
good first issue
invalid
pull-request
Mirrored from GitHub Pull Request
 question
stale
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-official-plugins#413
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?