mirror of
https://github.com/langgenius/dify-official-plugins.git
synced 2026-07-22 01:55:27 -04:00
[openai_api_compatible] Error: PluginInvokeError: {"args":{},"error_type":"TypeError","message":"'NoneType' object is not iterable"} in qwen-vl 2.5 #596
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 @zyy-hw on GitHub (Aug 27, 2025).
Self Checks
Dify version
main 8.1
Plugin version
openai_api_compatible 0.0.20
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Error log
Run failed: [openai_api_compatible] Error: PluginInvokeError: {"args":{},"error_type":"TypeError","message":"'NoneType' object is not iterable"}
@dosubot[bot] commented on GitHub (Aug 27, 2025):
Hi @zyy-hw! I'm Dosu and I’m helping the dify-official-plugins team.
This error is most likely caused by the plugin or backend returning None where an iterable (like a list or dict) is expected—often when parsing the model's response or handling workflow variables. For Qwen models, known issues include non-streaming mode incompatibility, missing expected fields in the response, or the backend closing the connection prematurely during non-streaming requests. Double-check that your backend supports non-streaming requests and returns the expected response structure (especially fields like
choices) source. Also, ensure your plugin configuration matches the backend's requirements, and consider debugging the workflow to trace variable values before plugin invocation source. If possible, try disabling streaming or switching to a market-provided OpenAI-API-compatible plugin for better compatibility source.To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

@zyy-hw commented on GitHub (Aug 27, 2025):
How to locate and confirm the place where this error occurs, currently with stream: true and the response structure is normal. @
How to locate and confirm the place where this error occurs, currently with stream: true and the response structure is normal.