mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-22 01:55:27 -04:00
bigbug，help #748
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @LauWoods on GitHub (Oct 24, 2025).
Self Checks
Dify version
1.8.1
Plugin version
langgenius-tongyi_0.0.56.difypkg
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Run failed: [tongyi] Error: req_id: f9873d95ab PluginInvokeError: {"args":{"description":"[models] Error: 'dict' object has no attribute 'dashscope_api_key'"},"error_type":"InvokeError","message":"[models] Error: 'dict' object has no attribute 'dashscope_api_key'"}
✔️ Error log
Run failed: [tongyi] Error: req_id: f9873d95ab PluginInvokeError: {"args":{"description":"[models] Error: 'dict' object has no attribute 'dashscope_api_key'"},"error_type":"InvokeError","message":"[models] Error: 'dict' object has no attribute 'dashscope_api_key'"}
@LauWoods commented on GitHub (Oct 24, 2025):
Error When Calling qwen-long via LLM Node (Other Qwen Models Work Fine)
When I call the qwen-longmodel through an LLM node, I encounter the following error. Other Qwen models do not produce this error.
Run failed: [tongyi] Error: req_id: bcb563d907 PluginInvokeError: {"args":{"description":"[models] Error: 'dict' object has no attribute 'dashscope_api_key'"},"error_type":"InvokeError","message":"[models] Error: 'dict' object has no attribute 'dashscope_api_key'"}
@dosubot[bot] commented on GitHub (Oct 24, 2025):
This error happens because the plugin code tries to access the DashScope API key using dot notation (
credentials.dashscope_api_key) when it should use dictionary key access (credentials['dashscope_api_key']). This bug is specific to the qwen-long model and has been reported by other users in self-hosted Docker environments. The robust fix is to patch the plugin code so all credential access uses dictionary keys, or to ensure credentials are always normalized before use. If you can't patch the code, workarounds include downgrading the Tongyi plugin to version 0.0.18 (which avoids the bug in some recent Dify releases), or switching the agent node strategy from EnhanceFunctionCalling to Dify's official agent strategy, but these do not always resolve the issue. Also, double-check that your API key is correctly configured and matches the expected format for DashScope. More details and user reports are available here and here.To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
@hjlarry commented on GitHub (Oct 28, 2025):
can't reproduce this, I think you can try a different version of tongyi plugin
@U11Leung commented on GitHub (Dec 12, 2025):
I can confirm in latest tongyi plugin 0.1.8, dify self-host 1.8.1, this issue still exist.
The key to reproducing the issue is it only occurs when a file is sent in user context:
The elapsed time is xx ms possibly indicating the message is returned from api.
Also, if the file is sent in system prompt, the error will change to UnsupportedDataType:
@U11Leung commented on GitHub (Dec 12, 2025):
I suggest the incompatibility be re-opened and re-investigate
@U11Leung commented on GitHub (Dec 12, 2025):
By requesting tongyi api directly (upload file and then use fileid to provide file content), I confirm qwen-long actually supports docx, xlsx, pdf, images