Run failed: 1 validation error for VariableMessage Value error, Only basic types and lists are allowed. [type=value_error, input_value={'variable_name': 'end', ...: None, 'stream': False}, input_type=dict] For further information visit https://errors.pydantic.dev/2.11/v/value_error

[changyuFU]

Self Checks

• 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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Errors that occurred after upgrading from version 1.7 to 1.11.1 of Dify

2. Additional context or comments

Errors that occurred after upgrading from version 1.7 to 1.11.1 of Dify

[dosubot[bot]]

Hi @changyuFU! I'm Dosu and I’m helping the dify team.

This error is caused by stricter type validation in Dify 1.11.1: tool parameters defined as string or select must now receive a string, not a dict or other structure. In older versions, this was more permissive. To fix it, make sure your workflow and agent configurations pass values that match the expected types for each tool parameter. For example, if a parameter is defined as a string, pass a string value; if you need to pass a dict, update the parameter type to OBJECT in your workflow tool config.

As a temporary workaround, you can set the tool_node_version field in your workflow or agent node configuration to None to restore legacy behavior and disable strict validation, but this may not be supported in future versions. Also, ensure that variables are not null—omit them or use a placeholder string if needed.

More details and step-by-step solutions are discussed here and you can review the relevant validation logic in the code here.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[changyuFU]

I still don't understand what I should do

[dosubot[bot]]

Here's what you need to do:

1. Find the parameter in your workflow or agent config that's causing the error. It's likely defined as a string or select type, but the value being passed is a dictionary (dict) instead of a string.
2. Change the value so it matches the expected type. For string/select parameters, pass a string (like "example"), not a dict (like {"key": "value"}). If you actually need to pass a dict, update the parameter type to OBJECT in your workflow tool config instead.
3. If you see this error because a variable is null, either remove that variable from the output or set it to a placeholder string (like "").

Example:

• Wrong (causes error):

  {
    "parameter_name": {"key": "value"}
  }

• Correct (for string/select type):

  {
    "parameter_name": "value"
  }

• If you need to pass a dict, change the parameter type to OBJECT.

As a temporary workaround, you can set the tool_node_version field in your workflow or agent node config to null (None). This will restore the old, more permissive behavior, but it's not guaranteed to work in future Dify versions.

If you want more specific help, share the part of your config or payload that's causing the error.

More details and examples are available in this discussion: GitHub issue #29682.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}