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

Azure Model plugin does not support files such as PDFs. #919

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

Originally created by @dimsky on GitHub (Jan 6, 2026).

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 Dify issues & Dify Official Plugins, 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.11.1

Plugin version

latest

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Current models such as Claude, GPT, and Gemini natively support the parsing of PDF and other files, so I don't need to go through any other steps for parsing.

✔️ Error log

No response

Originally created by @dimsky on GitHub (Jan 6, 2026). ### 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 [Dify issues](https://github.com/langgenius/dify/issues) & [Dify Official Plugins](https://github.com/langgenius/dify-official-plugins/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.11.1 ### Plugin version latest ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1535" height="787" alt="Image" src="https://github.com/user-attachments/assets/d0e573c5-fd80-490b-a6d4-59151a50a76a" /> Current models such as Claude, GPT, and Gemini natively support the parsing of PDF and other files, so I don't need to go through any other steps for parsing. ### ✔️ Error log _No response_
yindo added the bug label 2026-02-16 10:21:00 -05:00
yindo closed this issue 2026-02-16 10:21:00 -05:00
yindo commented 2026-02-16 10:21:01 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 6, 2026):

This is a known limitation: the Azure Model plugin in Dify does not support direct file inputs like PDFs. The plugin only handles text and image content in prompt messages—there’s no code to parse or upload PDF or other document files as input. If you pass a file variable (such as a PDF) directly to an LLM node, you’ll get an error because the node expects plain text, not a file object.

The officially supported workflow is to add a Document Extractor node to your pipeline: upload your PDF, extract the text, and then pass that text to the LLM node. Only the extracted text will be processed; image-based or scanned PDFs are not supported (no OCR is performed) — for those, you’ll need to run OCR externally before uploading the file reference.

Direct file input (beyond images) is not supported in agent applications or vision mode, and multimodal/file support for agent nodes is planned but not available yet. If you need direct PDF/file support, you’ll need to preprocess files into text or use a model/plugin that advertises native document support reference.

Let me know if you want guidance on alternative workflows or custom integrations.

To reply, just mention @dosu.

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

Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 6, 2026): <!-- Answer --> This is a known limitation: the Azure Model plugin in Dify does not support direct file inputs like PDFs. The plugin only handles text and image content in prompt messages—there’s no code to parse or upload PDF or other document files as input. If you pass a file variable (such as a PDF) directly to an LLM node, you’ll get an error because the node expects plain text, not a file object. The officially supported workflow is to add a Document Extractor node to your pipeline: upload your PDF, extract the text, and then pass that text to the LLM node. Only the extracted text will be processed; image-based or scanned PDFs are not supported (no OCR is performed) — for those, you’ll need to run OCR externally before uploading the file [reference](https://github.com/langgenius/dify/discussions/29878). Direct file input (beyond images) is not supported in agent applications or vision mode, and multimodal/file support for agent nodes is planned but not available yet. If you need direct PDF/file support, you’ll need to preprocess files into text or use a model/plugin that advertises native document support [reference](https://github.com/langgenius/dify-official-plugins/blob/04dcfdc4d2f2e2bba3829eaecb6089d587557267/models/azure_openai/models/llm/llm.py#L52-L1491). Let me know if you want guidance on alternative workflows or custom integrations. <!-- 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/5994d971-aa98-44d8-ae06-671889584a76?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5994d971-aa98-44d8-ae06-671889584a76?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5994d971-aa98-44d8-ae06-671889584a76?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5994d971-aa98-44d8-ae06-671889584a76?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5994d971-aa98-44d8-ae06-671889584a76?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5994d971-aa98-44d8-ae06-671889584a76?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5994d971-aa98-44d8-ae06-671889584a76?feedback_type=other)</sup> [![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20limitation%3A%20the%20Azure%20Model%20plugin%20in%20Dify%20does%20not%20support%20direct%20file%20inputs%20like%20PDFs.%20The%20plugin%20only%20handles%20text%20and%20image%20content%20in%20prompt%20messages%E2%80%94there%E2%80%99s%20no%20code%20to%20parse%20or%20upload%20PDF%20or%20other%20document%20files%20as%20input.%20If%20you%20pass%20a%20file%20variable%20%28such%20as%20a%20PDF%29%20directly%20to%20an%20LLM%20node%2C%20you%E2%80%99ll%20get%20an%20error%20because%20the%20node%20expects%20plain%20text%2C%20not%20a%20file%20object.%20%0A%0AThe%20officially%20supported%20workflow%20is%20to%20add%20a%20Document%20Extractor%20node%20to%20your%20pipeline%3A%20upload%20your%20PDF%2C%20extract%20the%20text%2C%20and%20then%20pass%20that%20text%20to%20the%20LLM%20node.%20Only%20the%20extracted%20text%20will%20be%20processed%3B%20image-based%20or%20scanned%20PDFs%20are%20not%20supported%20%28no%20OCR%20is%20performed%29%C2%A0%E2%80%94%C2%A0for%20those%2C%20you%E2%80%99ll%20need%20to%20run%20OCR%20externally%20before%20uploading%20the%20file%C2%A0%5Breference%5D%28https%3A//github.com/langgenius/dify/discussions/29878%29.%0A%0ADirect%20file%20input%20%28beyond%20images%29%20is%20not%20supported%20in%20agent%20applications%20or%20vision%20mode%2C%20and%20multimodal/file%20support%20for%20agent%20nodes%20is%20planned%20but%20not%20available%20yet.%20If%20you%20need%20direct%20PDF/file%20support%2C%20you%E2%80%99ll%20need%20to%20preprocess%20files%20into%20text%20or%20use%20a%20model/plugin%20that%20advertises%20native%20document%20support%C2%A0%5Breference%5D%28https%3A//github.com/langgenius/dify-official-plugins/blob/04dcfdc4d2f2e2bba3829eaecb6089d587557267/models/azure_openai/models/llm/llm.py%23L52-L1491%29.%0A%0ALet%20me%20know%20if%20you%20want%20guidance%20on%20alternative%20workflows%20or%20custom%20integrations.)&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-official-plugins/issues/2371)
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 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-official-plugins#919
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?