You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the workflow (chatflow) of Dify version 1.0.0 and attempting to use the official Agent policy group nodes of Dify to call the models deployed by Ollama, the models cannot be used correctly. The workflow originally expected to effectively call the Ollama-deployed models through the Agent policy group nodes for conversation interaction. However, an error occurred during the actual execution, resulting in the inability to use the model to complete the corresponding tasks normally. But models of the same type can execute the policy nodes normally when using a provider other than Ollama. This problem still exists in the newly released Agent strategy plugin of version 0.0.9.
II. Error Message
Run failed: Failed to transform agent message: PluginInvokeError: {"args":{},"error_type":"ValidationError","message":"1 validation error for FunctionCallingParams\nmodel.entity\n Input should be a valid dictionary or instance of AIModelEntity [type=model_type, input_value=None, input_type=NoneType]\n For further information visit https://errors.pydantic.dev/2.8/v/model_type"}
This error message indicates that there is a validation error in FunctionCallingParams. Specifically, the input of model.entity should be a valid dictionary or an instance of AIModelEntity, but the actual input is None.
The running status of the Ollama service has been checked, and it can normally respond to independent requests, indicating that the deployment and operation of Ollama itself are not problematic.
The model parameters of the Agent policy group nodes have been reconfigured, but the problem still persists.
I hope that the maintainers of the Dify project can help troubleshoot and solve this problem. Thank you very much! Please feel free to let me know if you need more information.
The text was updated successfully, but these errors were encountered:
I. Problem Description
When using the workflow (chatflow) of Dify version 1.0.0 and attempting to use the official Agent policy group nodes of Dify to call the models deployed by Ollama, the models cannot be used correctly. The workflow originally expected to effectively call the Ollama-deployed models through the Agent policy group nodes for conversation interaction. However, an error occurred during the actual execution, resulting in the inability to use the model to complete the corresponding tasks normally. But models of the same type can execute the policy nodes normally when using a provider other than Ollama. This problem still exists in the newly released Agent strategy plugin of version 0.0.9.
II. Error Message
Run failed: Failed to transform agent message: PluginInvokeError: {"args":{},"error_type":"ValidationError","message":"1 validation error for FunctionCallingParams\nmodel.entity\n Input should be a valid dictionary or instance of AIModelEntity [type=model_type, input_value=None, input_type=NoneType]\n For further information visit https://errors.pydantic.dev/2.8/v/model_type"}
This error message indicates that there is a validation error in FunctionCallingParams. Specifically, the input of model.entity should be a valid dictionary or an instance of AIModelEntity, but the actual input is None.
III.Environment Information
Operating System: [WSL2 Ubuntu 22.04 LTS]
Dify Version: 1.0.0
Ollama Version: [Ollama 0.15.2]
IVSupplementary Instructions
The running status of the Ollama service has been checked, and it can normally respond to independent requests, indicating that the deployment and operation of Ollama itself are not problematic.
The model parameters of the Agent policy group nodes have been reconfigured, but the problem still persists.
I hope that the maintainers of the Dify project can help troubleshoot and solve this problem. Thank you very much! Please feel free to let me know if you need more information.
The text was updated successfully, but these errors were encountered: