Dify Workflow Orchestrate can not be load when I update version from 0.7.3 to 0.10.2

[alieninsect]

Self Checks

• [X] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [X] I have searched for existing issues search for existing issues, including closed ones.
• [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [X] Please do not modify this template :) and fill in all the required fields.

Dify version

0.10.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

Hey, @alieninsect! 👋 I'm here to help you with any bugs, questions, or contributions. I'm a bot designed to assist you while you wait for a human maintainer.

I couldn't find specific error messages or logs related to the Dify Workflow Orchestrate component failing to load after upgrading to version 0.10.2. However, there are some known breaking changes and deprecations between versions 0.7.3 and 0.10.2. The image upload feature in Workflow's "Features" and the sys.files variable have been marked as LEGACY and will be deprecated in the future. Developers are encouraged to use custom file variables to add file upload functionality to Workflow applications ^[1].

Additionally, there is a closed issue related to various variable errors after upgrading to version 0.10.0, which might be relevant. The suggested solution involved addressing None values for certain fields using default values or handling them in the code ^[2].

If you haven't already, you might want to check your configuration and ensure that any deprecated features or variables are updated according to the latest version's requirements. If you encounter specific error messages, those could provide more clues for troubleshooting.

To continue talking to Dosu, mention @dosu.

[crazywoola]

I think this picture isn't enough to investigate this issue. If you encounter a 400 error, you can paste the call as cURL comand here.