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
The "Model schema not found" error in the chat interface, while the workflow functions correctly, could be due to differences in how the chat interface and workflow handle model configurations. Here are some potential causes and steps to troubleshoot:
Model Registration: Ensure that the model 'glm4' is correctly registered and available for the chat interface. The chat interface and workflow might have different configurations or access to models.
Configuration Differences: Check if there are any configuration differences between the chat interface and the workflow. The chat interface might require additional settings or credentials that are not needed for the workflow.
Model Schema Validation: Verify that the model schema is correctly defined and accessible in the chat interface. The error might indicate that the chat interface cannot find the necessary schema for 'glm4', possibly due to a misconfiguration or missing files.
Provider Credentials: Ensure that the provider credentials are correctly set up and validated for the chat interface. The workflow might be using a different set of credentials or a different validation process.
Docker Configuration: Since you are using Docker, ensure that the network settings and environment variables are correctly configured for both dify-web and dify-api images. The chat interface might be unable to access the model due to network restrictions or incorrect environment settings.
Review these areas to identify any discrepancies or missing configurations that could lead to the error in the chat interface.
本地化部署的dify的 聊天助手 和 Agent 应用中进行聊天报错如下:
大模型是使用ollama进行部署的
但是在工作流中又可以正常使用
本地部署的dify版本如下:
这是什么原因导致的?
The text was updated successfully, but these errors were encountered: