read llm model failed: request failed: [tongyi] Error: PluginInvokeError: {"args":{"description":"[models] Error: 'description'"},"error_type":"InvokeError #438

Closed
opened 2026-02-16 10:19:25 -05:00 by yindo · 2 comments
Owner

Originally created by @wangpanfeng158 on GitHub (Jul 10, 2025).

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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.

Dify version

1.5.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When I was using chatflow, I configured an agent node and used the qwen max latest model. The error message was: Run failed: Failed to transform agent message: PluginInvokeError: {"args":{},"error_type":"Exception","message":"read llm model failed: request failed: [tongyi] Error: PluginInvokeError: {"args":{"description":"[models] Error: 'description'"},"error_type":"InvokeError","message":"[models] Error: 'description'"}"}
Here is a screenshot

Image

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @wangpanfeng158 on GitHub (Jul 10, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.5.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When I was using chatflow, I configured an agent node and used the qwen max latest model. The error message was: Run failed: Failed to transform agent message: PluginInvokeError: {"args":{},"error_type":"Exception","message":"read llm model failed: request failed: [tongyi] Error: PluginInvokeError: {"args":{"description":"[models] Error: 'description'"},"error_type":"InvokeError","message":"[models] Error: 'description'"}"} Here is a screenshot <img width="786" height="706" alt="Image" src="https://github.com/user-attachments/assets/cf5ccfb0-4187-4df9-b04c-9b03e44733f5" /> ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo closed this issue 2026-02-16 10:19:25 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Jul 10, 2025):

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

This error is caused by the Tongyi (Qwen) plugin or model integration missing a required description field in its schema or manifest. Dify now expects this field for LLM plugins, and its absence leads to the PluginInvokeError you’re seeing. This is a known issue, especially with recent Dify versions and certain Tongyi plugin releases. Users have reported that some plugin versions (like 0.0.7 or 0.0.18) work, while others (such as 0.0.25) break compatibility with Qwen models in agent nodes or workflows. Upgrading or downgrading the Tongyi plugin, or reinstalling it from the Dify Marketplace, has resolved the issue for some users. Also, make sure the plugin was initialized with full network access so it could install all dependencies during setup. More details and user experiences are documented here, here, and here.

If you’re using MCP or structured output features, be aware that the official Tongyi plugin may not be fully compatible, as it tries to access the description field in each property and fails if it’s missing. The Qwen model from the Tongyi provider works in some configurations, but plugin version and Dify version compatibility are key factors source.

Try rolling back to a known working Tongyi plugin version (such as 0.0.18), or reinstall the plugin from the Marketplace. If you built or installed the plugin in an environment with network restrictions, ensure it can access the internet and reinitialize it. If you have custom model schemas or plugin manifests, make sure they include a description field for each model property.

Let me know if you need a sample schema or more details on plugin configuration.

To reply, just mention @dosu.


How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 10, 2025): <!-- Greeting --> Hi @wangpanfeng158! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This error is caused by the Tongyi (Qwen) plugin or model integration missing a required description field in its schema or manifest. Dify now expects this field for LLM plugins, and its absence leads to the PluginInvokeError you’re seeing. This is a known issue, especially with recent Dify versions and certain Tongyi plugin releases. Users have reported that some plugin versions (like 0.0.7 or 0.0.18) work, while others (such as 0.0.25) break compatibility with Qwen models in agent nodes or workflows. Upgrading or downgrading the Tongyi plugin, or reinstalling it from the Dify Marketplace, has resolved the issue for some users. Also, make sure the plugin was initialized with full network access so it could install all dependencies during setup. More details and user experiences are documented [here](https://github.com/langgenius/dify/issues/19712), [here](https://github.com/langgenius/dify/issues/20946), and [here](https://github.com/langgenius/dify/issues/18795). If you’re using MCP or structured output features, be aware that the official Tongyi plugin may not be fully compatible, as it tries to access the description field in each property and fails if it’s missing. The Qwen model from the Tongyi provider works in some configurations, but plugin version and Dify version compatibility are key factors [source](https://github.com/langgenius/dify/issues/20946). Try rolling back to a known working Tongyi plugin version (such as 0.0.18), or reinstall the plugin from the Marketplace. If you built or installed the plugin in an environment with network restrictions, ensure it can access the internet and reinitialize it. If you have custom model schemas or plugin manifests, make sure they include a description field for each model property. Let me know if you need a sample schema or more details on plugin configuration. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/a08a40b7-d508-4e15-a05d-9e52ae0b2943?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a08a40b7-d508-4e15-a05d-9e52ae0b2943?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a08a40b7-d508-4e15-a05d-9e52ae0b2943?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a08a40b7-d508-4e15-a05d-9e52ae0b2943?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a08a40b7-d508-4e15-a05d-9e52ae0b2943?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a08a40b7-d508-4e15-a05d-9e52ae0b2943?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a08a40b7-d508-4e15-a05d-9e52ae0b2943?feedback_type=other)</sup>&nbsp;&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/22166)
Author
Owner

@wangpanfeng158 commented on GitHub (Jul 10, 2025):

Thank you very much. I chose Dify's official agent strategy in the agent and solved this problem

@wangpanfeng158 commented on GitHub (Jul 10, 2025): Thank you very much. I chose Dify's official agent strategy in the agent and solved this problem
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-official-plugins#438