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

File upload issue in conversation #7384

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

Originally created by @Dongnc1017 on GitHub (Dec 25, 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.14.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

If you delete the file uploaded in the first conversation and re-upload the second one, the result is still a question and answer based on the first file. Does the default support only support multiple rounds of conversations with a single file? Files cannot be deleted and re-uploaded in the middle of a conversation

✔️ Expected Behavior

The first conversation file is uploaded, and questions and answers can be conducted normally with the content of the file still intact. Delete the file and continue uploading, and answer based on the newly uploaded file.

❌ Actual Behavior

The first conversation file is uploaded, and questions and answers can be conducted normally with the content of the file still intact. If you delete the file and continue uploading, the contents of the first file will still be there.

Originally created by @Dongnc1017 on GitHub (Dec 25, 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.14.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce If you delete the file uploaded in the first conversation and re-upload the second one, the result is still a question and answer based on the first file. Does the default support only support multiple rounds of conversations with a single file? Files cannot be deleted and re-uploaded in the middle of a conversation ### ✔️ Expected Behavior The first conversation file is uploaded, and questions and answers can be conducted normally with the content of the file still intact. Delete the file and continue uploading, and answer based on the newly uploaded file. ### ❌ Actual Behavior The first conversation file is uploaded, and questions and answers can be conducted normally with the content of the file still intact. If you delete the file and continue uploading, the contents of the first file will still be there.
yindo added the 🐞 bug label 2026-02-21 18:20:19 -05:00
yindo closed this issue 2026-02-21 18:20:19 -05:00
yindo commented 2026-02-21 18:20:19 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 25, 2024):

I found a similar closed issue that might be relevant to your problem. The issue discussed a similar problem where the file parameter was not consistent between the conversation and the file upload part. The suggested solution was to check the handleRemoveFile function, which might not be updating the state correctly or clearing the sys.files variable. It was recommended to check for any updates or patches for your version of Dify, or to adjust any additional settings or configurations that might be affecting this behavior [1].

Additionally, you might want to review the configurations related to file uploads and removals in Dify. These include settings like enabling file uploads in the ChatFlow application, using file variables in the Start Node, and ensuring proper text extraction from files [2].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Dec 25, 2024): <!-- Answer --> I found a similar closed issue that might be relevant to your problem. The issue discussed a similar problem where the file parameter was not consistent between the conversation and the file upload part. The suggested solution was to check the `handleRemoveFile` function, which might not be updating the state correctly or clearing the `sys.files` variable. It was recommended to check for any updates or patches for your version of Dify, or to adjust any additional settings or configurations that might be affecting this behavior <sup>[[1]](https://github.com/langgenius/dify/issues/10393)</sup>. Additionally, you might want to review the configurations related to file uploads and removals in Dify. These include settings like enabling file uploads in the ChatFlow application, using file variables in the Start Node, and ensuring proper text extraction from files <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.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/165cc195-2ef2-4459-a25a-3f1ea1e70768?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/165cc195-2ef2-4459-a25a-3f1ea1e70768?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/165cc195-2ef2-4459-a25a-3f1ea1e70768?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/165cc195-2ef2-4459-a25a-3f1ea1e70768?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/165cc195-2ef2-4459-a25a-3f1ea1e70768?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/165cc195-2ef2-4459-a25a-3f1ea1e70768?feedback_type=other)</sup>
yindo commented 2026-02-21 18:20:20 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 25, 2024):

This is not a bug actually, we have an https://github.com/langgenius/dify/discussions/10652 here. Not only you can not change the uploaded file but also other parameters at the beginning.

@crazywoola commented on GitHub (Dec 25, 2024): This is not a bug actually, we have an https://github.com/langgenius/dify/discussions/10652 here. Not only you can not change the uploaded file but also other parameters at the beginning.
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#7384
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?