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

Bug: Most Workflow Nodes Fail to Retrieve Image Data in Self-Hosted Dify 0.10.0 #6202

New Issue
Closed
opened 2026-02-21 18:14:32 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:14:32 -05:00
Owner
Copy Link
Copy Source

Originally created by @Halflifefa on GitHub (Oct 21, 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.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Update the Dify installation to version 0.10.0 in a self-hosted environment.
  2. Configure a workflow with different types of nodes:
    • Code Execution
    • HTTP Requests
    • Tool Calls (e.g., external integrations)
    • Direct Reply
  3. Upload or attempt to pass image files through these nodes.
  4. Observe the outputs from these nodes.

✔️ Expected Behavior

  • All workflow nodes should correctly retrieve and process image data or URLs passed through them.

❌ Actual Behavior

  • Most nodes (e.g., Code Execution, HTTP Requests, Tool Calls) return null when trying to access image data.
  • Only the Direct Reply node can retrieve content, but the URL field remains null.
    image1
    image2
Originally created by @Halflifefa on GitHub (Oct 21, 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.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Update the Dify installation to version 0.10.0 in a self-hosted environment. 2. Configure a workflow with different types of nodes: - Code Execution - HTTP Requests - Tool Calls (e.g., external integrations) - Direct Reply 3. Upload or attempt to pass image files through these nodes. 4. Observe the outputs from these nodes. ### ✔️ Expected Behavior - All workflow nodes should correctly retrieve and process image data or URLs passed through them. ### ❌ Actual Behavior - Most nodes (e.g., Code Execution, HTTP Requests, Tool Calls) return `null` when trying to access image data. - Only the **Direct Reply** node can retrieve content, but the URL field remains `null`. ![image1](https://github.com/user-attachments/assets/38680b2a-70f1-4dd7-b2e5-6c45bccba5f5) ![image2](https://github.com/user-attachments/assets/bd1411e4-0b4c-48d0-9c7b-c7330639f894)
yindo added the 🐞 bug label 2026-02-21 18:14:32 -05:00
yindo closed this issue 2026-02-21 18:14:32 -05:00
yindo commented 2026-02-21 18:14:32 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 21, 2024):

There are no specific issues or limitations documented regarding image data handling in version 0.10.0 of the Dify codebase. However, the image upload feature has been replaced by a more comprehensive "file upload" feature, and the previous image upload functionality is now part of this broader feature. The image upload feature in Workflow applications is marked as LEGACY and will be deprecated in the future, suggesting developers transition to using custom file variables for file uploads [1][2].

Given the issue you're experiencing, it might be related to this transition. Ensure that your workflow is configured to use the new file upload feature and that the nodes are correctly set up to handle the sys.files variable, which stores uploaded image files. Additionally, check if the MULTIMODAL_SEND_IMAGE_FORMAT and UPLOAD_IMAGE_FILE_SIZE_LIMIT configurations are set appropriately in your self-hosted environment [3].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Oct 21, 2024): <!-- Answer --> There are no specific issues or limitations documented regarding image data handling in version 0.10.0 of the Dify codebase. However, the image upload feature has been replaced by a more comprehensive "file upload" feature, and the previous image upload functionality is now part of this broader feature. The image upload feature in Workflow applications is marked as `LEGACY` and will be deprecated in the future, suggesting developers transition to using custom file variables for file uploads <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/zh_CN/guides/workflow/bulletin.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/bulletin.md)</sup>. Given the issue you're experiencing, it might be related to this transition. Ensure that your workflow is configured to use the new file upload feature and that the nodes are correctly set up to handle the `sys.files` variable, which stores uploaded image files. Additionally, check if the `MULTIMODAL_SEND_IMAGE_FORMAT` and `UPLOAD_IMAGE_FILE_SIZE_LIMIT` configurations are set appropriately in your self-hosted environment <sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/environments.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:14:32 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Oct 21, 2024):

Duplicated https://github.com/langgenius/dify/issues/9567

@crazywoola commented on GitHub (Oct 21, 2024): Duplicated https://github.com/langgenius/dify/issues/9567
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#6202
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?