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

Agent node and LLM node cannot read multi-modal content at a correct turn #13371

New Issue
Open
opened 2026-02-21 19:11:51 -05:00 by yindo · 11 comments
yindo commented 2026-02-21 19:11:51 -05:00
Owner
Copy Link
Copy Source

Originally created by @fdb02983rhy on GitHub (Apr 25, 2025).

Originally assigned to: @Nov1c444 on GitHub.

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @fdb02983rhy on GitHub (Apr 25, 2025). Originally assigned to: @Nov1c444 on GitHub. ### 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.3.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/5b6b1ea5-569c-42c8-ab68-17a8f59e37a9) ![Image](https://github.com/user-attachments/assets/de518f78-6045-448d-a88e-3921640c3cc8) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo commented 2026-02-21 19:11:51 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 25, 2025):

To address the issue of the agent node not being able to read multimodal content, here are some steps and considerations:

  1. Check Model Settings: Ensure that the model settings for multimodal content are correctly configured. This includes enabling Vision multimodal support and setting the MULTIMODAL_SEND_FORMAT to either base64 or url. If using url, make sure FILES_URL is set to an externally accessible address [1].

  2. File Type Conditions: Verify that the workflow editor interface is correctly handling file type conditions. You should be able to set conditions based on file attributes such as type, extension, and MIME type. Ensure that the conditions for PDFs and images are properly configured [2].

  3. Error Logs and Messages: Review any error logs or messages generated during the process. Although specific error messages related to multimodal content processing weren't found, checking logs for any indications of issues can be helpful.

  4. Known Issues: Be aware of known issues related to multimodal content processing, such as unsupported file formats or size limits, S3 bucket upload issues, and AWS SageMaker endpoint setup problems [3].

By following these steps, you should be able to diagnose and potentially resolve the issue with the agent node's inability to read multimodal content.

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 (Apr 25, 2025): <!-- Answer --> To address the issue of the agent node not being able to read multimodal content, here are some steps and considerations: 1. **Check Model Settings**: Ensure that the model settings for multimodal content are correctly configured. This includes enabling Vision multimodal support and setting the `MULTIMODAL_SEND_FORMAT` to either `base64` or `url`. If using `url`, make sure `FILES_URL` is set to an externally accessible address <sup>[[1]](https://github.com/langgenius/dify-docs/issues/433)</sup>. 2. **File Type Conditions**: Verify that the workflow editor interface is correctly handling file type conditions. You should be able to set conditions based on file attributes such as type, extension, and MIME type. Ensure that the conditions for PDFs and images are properly configured <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/node/list-operator.md)</sup>. 3. **Error Logs and Messages**: Review any error logs or messages generated during the process. Although specific error messages related to multimodal content processing weren't found, checking logs for any indications of issues can be helpful. 4. **Known Issues**: Be aware of known issues related to multimodal content processing, such as unsupported file formats or size limits, S3 bucket upload issues, and AWS SageMaker endpoint setup problems <sup>[[3]](https://github.com/langgenius/dify/issues/11567)</sup>. By following these steps, you should be able to diagnose and potentially resolve the issue with the agent node's inability to read multimodal content. <!-- 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/c9a04a20-e1a6-4fec-906f-64971c1c037f?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/c9a04a20-e1a6-4fec-906f-64971c1c037f?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/c9a04a20-e1a6-4fec-906f-64971c1c037f?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/c9a04a20-e1a6-4fec-906f-64971c1c037f?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c9a04a20-e1a6-4fec-906f-64971c1c037f?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/c9a04a20-e1a6-4fec-906f-64971c1c037f?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c9a04a20-e1a6-4fec-906f-64971c1c037f?feedback_type=other)</sup>
yindo commented 2026-02-21 19:11:51 -05:00
Author
Owner
Copy Link
Copy Source

@AAlexDing commented on GitHub (Jun 8, 2025):

It seems that the Dify team has not tested the multimodal logic of the agent node. Although the agent node has been launched, it remains in an unusable state.

@AAlexDing commented on GitHub (Jun 8, 2025): It seems that the Dify team has not tested the multimodal logic of the agent node. Although the agent node has been launched, it remains in an unusable state.
yindo commented 2026-02-21 19:11:51 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Jun 9, 2025):

@laipz8200 Hi, is this feature on the roadmap by any change?

@fdb02983rhy commented on GitHub (Jun 9, 2025): @laipz8200 Hi, is this feature on the roadmap by any change?
yindo commented 2026-02-21 19:11:51 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 28, 2025):

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

Issue Summary:

  • You reported that in Dify v1.3.0 self-hosted via Docker, the agent node cannot read multimodal content.
  • The expected and actual behavior details were not fully provided.
  • I suggested checking model settings, file types, error logs, and known issues.
  • A contributor mentioned that the multimodal logic for the agent node has not been tested and is currently unusable.
  • You asked if support for this feature is planned for future development.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here.
  • If I do not hear back within 15 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 28, 2025): Hi, @fdb02983rhy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that in Dify v1.3.0 self-hosted via Docker, the agent node cannot read multimodal content. - The expected and actual behavior details were not fully provided. - I suggested checking model settings, file types, error logs, and known issues. - A contributor mentioned that the multimodal logic for the agent node has not been tested and is currently unusable. - You asked if support for this feature is planned for future development. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here. - If I do not hear back within 15 days, this issue will be automatically closed. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:11:51 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Aug 29, 2025):

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

Issue Summary:

  • You reported that in Dify v1.3.0 self-hosted via Docker, the agent node cannot read multimodal content.
  • The expected and actual behavior details were not fully provided.
  • I suggested checking model settings, file types, error logs, and known issues.
  • A contributor mentioned that the multimodal logic for the agent node has not been tested and is currently unusable.
  • You asked if support for this feature is planned for future development.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here.
  • If I do not hear back within 15 days, this issue will be automatically closed.

Thank you for your understanding and contribution!

Yes, and the issue is Agent node and LLM node cannot read multi-modal content at a correct turn, Agent Node Cannot Read MultiModal Content is just one of the symptoms.

@fdb02983rhy commented on GitHub (Aug 29, 2025): > Hi, [@fdb02983rhy](https://github.com/fdb02983rhy). I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. > > **Issue Summary:** > > * You reported that in Dify v1.3.0 self-hosted via Docker, the agent node cannot read multimodal content. > * The expected and actual behavior details were not fully provided. > * I suggested checking model settings, file types, error logs, and known issues. > * A contributor mentioned that the multimodal logic for the agent node has not been tested and is currently unusable. > * You asked if support for this feature is planned for future development. > > **Next Steps:** > > * Please let me know if this issue is still relevant with the latest version of Dify by commenting here. > * If I do not hear back within 15 days, this issue will be automatically closed. > > Thank you for your understanding and contribution! Yes, and the issue is Agent node and LLM node cannot read multi-modal content at a correct turn, Agent Node Cannot Read MultiModal Content is just one of the symptoms.
yindo commented 2026-02-21 19:11:52 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 29, 2025):

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

Issue Summary:

  • You reported that in Dify v1.3.0 self-hosted via Docker, the agent node cannot properly read multimodal content.
  • Related issues also affect the LLM node's handling of multimodal content.
  • Contributor AAlexDing noted the multimodal logic for the agent node is untested and currently unusable.
  • You confirmed the issue persists and is broader than just the agent node.
  • Troubleshooting steps were provided earlier, but no resolution has been reached yet.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of Dify by commenting here.
  • If I do not receive a response, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 29, 2025): Hi, @fdb02983rhy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that in Dify v1.3.0 self-hosted via Docker, the agent node cannot properly read multimodal content. - Related issues also affect the LLM node's handling of multimodal content. - Contributor AAlexDing noted the multimodal logic for the agent node is untested and currently unusable. - You confirmed the issue persists and is broader than just the agent node. - Troubleshooting steps were provided earlier, but no resolution has been reached yet. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of Dify by commenting here. - If I do not receive a response, I will automatically close this issue in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:11:52 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Sep 29, 2025):

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

Issue Summary:

  • You reported that in Dify v1.3.0 self-hosted via Docker, the agent node cannot properly read multimodal content.
  • Related issues also affect the LLM node's handling of multimodal content.
  • Contributor AAlexDing noted the multimodal logic for the agent node is untested and currently unusable.
  • You confirmed the issue persists and is broader than just the agent node.
  • Troubleshooting steps were provided earlier, but no resolution has been reached yet.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of Dify by commenting here.
  • If I do not receive a response, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

Yes

@fdb02983rhy commented on GitHub (Sep 29, 2025): > Hi, [@fdb02983rhy](https://github.com/fdb02983rhy). I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. > > **Issue Summary:** > > * You reported that in Dify v1.3.0 self-hosted via Docker, the agent node cannot properly read multimodal content. > * Related issues also affect the LLM node's handling of multimodal content. > * Contributor AAlexDing noted the multimodal logic for the agent node is untested and currently unusable. > * You confirmed the issue persists and is broader than just the agent node. > * Troubleshooting steps were provided earlier, but no resolution has been reached yet. > > **Next Steps:** > > * Please confirm if this issue is still relevant with the latest version of Dify by commenting here. > * If I do not receive a response, I will automatically close this issue in 15 days. > > Thank you for your understanding and contribution! Yes
yindo commented 2026-02-21 19:11:52 -05:00
Author
Owner
Copy Link
Copy Source

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

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

Issue Summary:

  • You reported that in Dify v1.3.0 self-hosted via Docker, both the agent node and LLM node fail to correctly process multimodal content in the proper turn.
  • Contributor AAlexDing noted that the multimodal logic for the agent node is untested and currently unusable.
  • Troubleshooting steps were provided, and the issue was previously marked as stale pending confirmation.
  • You confirmed the issue remains relevant and is broader than initially described.
  • The issue is currently unresolved.

Next Steps:

  • Please confirm if this issue still occurs with the latest version of Dify.
  • If it is still relevant, you can keep the discussion open by commenting on this issue; otherwise, I will automatically close it in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Jan 2, 2026): Hi, @fdb02983rhy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that in Dify v1.3.0 self-hosted via Docker, both the agent node and LLM node fail to correctly process multimodal content in the proper turn. - Contributor AAlexDing noted that the multimodal logic for the agent node is untested and currently unusable. - Troubleshooting steps were provided, and the issue was previously marked as stale pending confirmation. - You confirmed the issue remains relevant and is broader than initially described. - The issue is currently unresolved. **Next Steps:** - Please confirm if this issue still occurs with the latest version of Dify. - If it is still relevant, you can keep the discussion open by commenting on this issue; otherwise, I will automatically close it in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:11:52 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Jan 2, 2026):

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

Issue Summary:

  • You reported that in Dify v1.3.0 self-hosted via Docker, both the agent node and LLM node fail to correctly process multimodal content in the proper turn.
  • Contributor AAlexDing noted that the multimodal logic for the agent node is untested and currently unusable.
  • Troubleshooting steps were provided, and the issue was previously marked as stale pending confirmation.
  • You confirmed the issue remains relevant and is broader than initially described.
  • The issue is currently unresolved.

Next Steps:

  • Please confirm if this issue still occurs with the latest version of Dify.
  • If it is still relevant, you can keep the discussion open by commenting on this issue; otherwise, I will automatically close it in 15 days.

Thank you for your understanding and contribution!

yes

@fdb02983rhy commented on GitHub (Jan 2, 2026): > Hi, [@fdb02983rhy](https://github.com/fdb02983rhy). I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. > > **Issue Summary:** > > * You reported that in Dify v1.3.0 self-hosted via Docker, both the agent node and LLM node fail to correctly process multimodal content in the proper turn. > * Contributor AAlexDing noted that the multimodal logic for the agent node is untested and currently unusable. > * Troubleshooting steps were provided, and the issue was previously marked as stale pending confirmation. > * You confirmed the issue remains relevant and is broader than initially described. > * The issue is currently unresolved. > > **Next Steps:** > > * Please confirm if this issue still occurs with the latest version of Dify. > * If it is still relevant, you can keep the discussion open by commenting on this issue; otherwise, I will automatically close it in 15 days. > > Thank you for your understanding and contribution! yes
yindo commented 2026-02-21 19:11:52 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 2, 2026):

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

Issue Summary:

  • You reported that in Dify v1.3.0 self-hosted via Docker, both the agent node and LLM node fail to process multimodal content correctly in the proper turn.
  • Contributor AAlexDing noted that the multimodal logic for the agent node is currently untested and unusable.
  • I provided troubleshooting steps and marked the issue as stale multiple times pending your confirmation.
  • You confirmed the issue remains relevant and unresolved.
  • Maintainers are waiting to know if this problem persists in the latest version before proceeding.

Next Steps:

  • Please confirm if this issue is still present in the latest version of Dify by commenting on this issue.
  • If no response is received within 15 days, I will automatically close the issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 2, 2026): Hi, @fdb02983rhy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that in Dify v1.3.0 self-hosted via Docker, both the agent node and LLM node fail to process multimodal content correctly in the proper turn. - Contributor AAlexDing noted that the multimodal logic for the agent node is currently untested and unusable. - I provided troubleshooting steps and marked the issue as stale multiple times pending your confirmation. - You confirmed the issue remains relevant and unresolved. - Maintainers are waiting to know if this problem persists in the latest version before proceeding. **Next Steps:** - Please confirm if this issue is still present in the latest version of Dify by commenting on this issue. - If no response is received within 15 days, I will automatically close the issue. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:11:52 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (Feb 2, 2026):

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

Issue Summary:

  • You reported that in Dify v1.3.0 self-hosted via Docker, both the agent node and LLM node fail to process multimodal content correctly in the proper turn.
  • Contributor AAlexDing noted that the multimodal logic for the agent node is currently untested and unusable.
  • I provided troubleshooting steps and marked the issue as stale multiple times pending your confirmation.
  • You confirmed the issue remains relevant and unresolved.
  • Maintainers are waiting to know if this problem persists in the latest version before proceeding.

Next Steps:

  • Please confirm if this issue is still present in the latest version of Dify by commenting on this issue.
  • If no response is received within 15 days, I will automatically close the issue.

Thank you for your understanding and contribution!

yes

@fdb02983rhy commented on GitHub (Feb 2, 2026): > Hi, @fdb02983rhy. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. > > **Issue Summary:** > - You reported that in Dify v1.3.0 self-hosted via Docker, both the agent node and LLM node fail to process multimodal content correctly in the proper turn. > - Contributor AAlexDing noted that the multimodal logic for the agent node is currently untested and unusable. > - I provided troubleshooting steps and marked the issue as stale multiple times pending your confirmation. > - You confirmed the issue remains relevant and unresolved. > - Maintainers are waiting to know if this problem persists in the latest version before proceeding. > > **Next Steps:** > - Please confirm if this issue is still present in the latest version of Dify by commenting on this issue. > - If no response is received within 15 days, I will automatically close the issue. > > Thank you for your understanding and contribution! yes
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
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#13371
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?