Cannot display workflow page

[KazuSh1geru]

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

Cloud or Self Hosted

Cloud

Steps to reproduce

Go to specific tool page, https://cloud.dify.ai/app//workflow

error log

1 validation error for LLMNodeData vision.configs Input should be a valid dictionary or instance of VisionConfigOptions [type=model_type, input_value=None, input_type=NoneType] For further information visit https://errors.pydantic.dev/2.9/v/model_type

✔️ Expected Behavior

Go to workflow edit page.

❌ Actual Behavior

cannot display edit workflow page.

Application error: a client-side exception has occurred (see the browser console for more information).

[dosubot[bot]]

Hey @KazuSh1geru! 👋 I'm here to help you with bugs, questions, and more while you wait for a human maintainer. I'm Dosu, a bot designed to assist you.

I found a similar issue related to client-side exceptions in the Dify platform. The error message you're encountering seems to be related to the LLMNodeData class, specifically with the vision.configs attribute. The error indicates that the input should be a valid dictionary or an instance of VisionConfigOptions.

To resolve this issue, ensure that the vision.configs attribute in your workflow is correctly configured as a dictionary or an instance of VisionConfigOptions. This might involve checking the configuration settings in your workflow to ensure they align with the expected structure for VisionConfigOptions ^[1].

If you have access to the code or configuration files, you might want to verify that the VisionConfig is properly initialized with the correct options. If the issue persists, reviewing the browser console for additional error details might provide more insights into the specific configuration problem.

To continue talking to Dosu, mention @dosu.