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

Problem in the workflow conversation #6643

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

Originally created by @sandycs-protoss on GitHub (Nov 9, 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.11.0

Cloud or Self Hosted

Cloud

Steps to reproduce

Previous problem
In this multi-turn dialogue workflow, I use the image_file variable to upload image URLs. However, I've noticed that it consistently references the URL of the first uploaded image. In other words, once an image is uploaded, even if I subsequently upload different image URLs, the logs show that it always calls the image URL that was initially provided in this conversation.

Current problem
I've been asked to send the image file via "Files" like this:

{
  "inputs": {
    
  },
  "query": "Analyse this picture",
  "response_mode": "blocking",
  "conversation_id": "e5088572-49f7-4f9f-88c1-4d3eed8c1f9f",
  "auto_generate_name": false,
  "user": "wechatbot",
  "files": [
      {
         "type":"image",
    "transfer_method":"remote_url",
    "url":"https://img.calceus.org/wechat/2270171153495604502.jpg?x-oss-process=image/resize,w_1500"
      }
    ]
}

However, when I check the log in workflow, there is nothing in the sys.files.
This means that the files I'm passing in are completely ineffective.

My conversation ID is: e5088572-49f7-4f9f-88c1-4d3eed8c1f9f

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @sandycs-protoss on GitHub (Nov 9, 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.11.0 ### Cloud or Self Hosted Cloud ### Steps to reproduce **Previous problem** In this multi-turn dialogue workflow, I use the image_file variable to upload image URLs. However, I've noticed that it consistently references the URL of the first uploaded image. In other words, once an image is uploaded, even if I subsequently upload different image URLs, the logs show that it always calls the image URL that was initially provided in this conversation. **Current problem** I've been asked to send the image file via "Files" like this: ``` { "inputs": { }, "query": "Analyse this picture", "response_mode": "blocking", "conversation_id": "e5088572-49f7-4f9f-88c1-4d3eed8c1f9f", "auto_generate_name": false, "user": "wechatbot", "files": [ { "type":"image", "transfer_method":"remote_url", "url":"https://img.calceus.org/wechat/2270171153495604502.jpg?x-oss-process=image/resize,w_1500" } ] } ``` **However, when I check the log in workflow, there is nothing in the sys.files.** This means that the files I'm passing in are completely ineffective. My conversation ID is: e5088572-49f7-4f9f-88c1-4d3eed8c1f9f ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:16:41 -05:00
yindo closed this issue 2026-02-21 18:16:41 -05:00
yindo commented 2026-02-21 18:16:41 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 9, 2024):

The issue you're experiencing with the sys.files variable in Dify version 0.11.0 is likely due to the fact that the sys.files variable and the image upload feature have been marked as LEGACY and are set to be deprecated. The recommended approach now is to use custom file variables for file uploads in Workflow applications. This change means that the sys.files log may not capture uploads using the image_file variable, as the system is transitioning away from this legacy feature.

To resolve this, you should create a file-type variable in the "Start" node and reference this file variable in subsequent nodes instead of using the sys.files variable. Ensure that you are using the correct method for file uploads as described in the Dify documentation. For Workflow applications, add file variables in the "Start" node and use them in LLM nodes, especially for image files, by enabling the vision feature in the LLM node [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Nov 9, 2024): <!-- Answer --> The issue you're experiencing with the `sys.files` variable in Dify version 0.11.0 is likely due to the fact that the `sys.files` variable and the image upload feature have been marked as `LEGACY` and are set to be deprecated. The recommended approach now is to use custom file variables for file uploads in Workflow applications. This change means that the `sys.files` log may not capture uploads using the `image_file` variable, as the system is transitioning away from this legacy feature. To resolve this, you should create a file-type variable in the "Start" node and reference this file variable in subsequent nodes instead of using the `sys.files` variable. Ensure that you are using the correct method for file uploads as described in the Dify documentation. For Workflow applications, add file variables in the "Start" node and use them in LLM nodes, especially for image files, by enabling the vision feature in the LLM node <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/bulletin.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/guides/workflow/file-upload.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
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#6643
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?