Dify v1.0.0 cannot process messages with files

[Yeha-Truong]

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

Version 1.0.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Run Dify via Docker with the following version on the main branch: 252d2c425bb9a824fce6b3e5a8c4f09caf88b11f

✔️ Expected Behavior

The model should be able to process chat messages.

❌ Actual Behavior

[dosubot]

@Yeha-Truong Hello there! I'm here to help you with any bugs, questions, or contributions you have for Dify. I'll assist you while we wait for a human maintainer.

I found some similar closed issues that might help you address the problem:

1. Workflow Execution Failure with File Upload Operation: The suggested solution includes ensuring that the file is fully processed before initiating the workflow, verifying the JSON structure, and checking that all required fields are correctly filled ^[1].

2. Post /workflows/run with a remote URL throws bad_request 400: This issue suggests checking the JSON formatting, ensuring the Content-Type header is set to application/json, and verifying that the URL in the files array is correctly encoded ^[2].

Additionally, for handling image file uploads in Dify v1.0.0, ensure that you have enabled the "File Upload" feature in your application settings. This feature supports various file types, including images, and consolidates all file uploads under a single feature. You should also ensure that the file variables are correctly processed in the workflow, especially when using LLM nodes that support vision capabilities ^[3][4][5].

Regarding the Pydantic serialization warnings, it seems there might be a mismatch in the expected data types. The PromptMessageContent should be structured with a type of PromptMessageContentType and data as a string. Ensure that the data being passed matches these expectations ^[4][3][6].

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}

[laipz8200]

Thank you for your report. The hash version of the Docker image is not guaranteed to be stable; please follow our released tags.

[Yeha-Truong]

This bug still happens in the latest release v1.0.0