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
{{ message }}
Repository navigation
fix(gemini): gemini-3-pro-preview function call is missing a thought_signature in functionCall parts. #2088
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
v1.9.1
Plugin version
0.6.0
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
✔️ Error log
Run failed: Failed to transform agent message: req_id: b70298d58e PluginInvokeError: {"args":{},"error_type":"Exception","message":"read llm model failed: request failed: [google] Error: req_id: f1c9eb12f8 PluginInvokeError: {\"args\":{},\"error_type\":\"ClientError\",\"message\":\"400 INVALID_ARGUMENT. {'error': {'code': 400, 'message': 'Function call is missing a thought_signature in functionCall parts. This is required for tools to work correctly, and missing thought_signature may lead to degraded model performance. Additional data, function call `default_api:current_time` , position 4. please refer to https://ai.google.dev/gemini-api/docs/thought-signatures for more details.', 'status': 'INVALID_ARGUMENT'}}\"}"}
Hi, @QIN2DIM. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
You reported a bug in the gemini-3-pro-preview plugin where a missing thought_signature in functionCall parts causes a 400 INVALID_ARGUMENT error.
This error degrades model performance in a self-hosted Docker setup.
Other users like gabecowan and migege have confirmed experiencing the same issue.
Contributor laipz8200 mentioned some bypass methods as temporary workarounds.
The issue remains unresolved with ongoing community interest.
Next Steps:
Please let me know if this issue is still relevant with the latest version of the dify-official-plugins repository by commenting here to keep the discussion open.
If I do not hear back within 5 days, I will automatically close this issue.
Thank you for your understanding and contribution!
Activity
gabecowan commentedon Nov 20, 2025
Same issue for us.
migege commentedon Nov 25, 2025
Same issue, looking forward to getting it fixed
QIN2DIM commentedon Nov 25, 2025
@laipz8200
laipz8200 commentedon Nov 27, 2025
It seems we have found some bypass methods. I suggest using this method first.
dosubot commentedon Dec 13, 2025
Hi, @QIN2DIM. I'm Dosu, and I'm helping the dify-official-plugins team manage their backlog and am marking this issue as stale.
Issue Summary:
Next Steps:
Thank you for your understanding and contribution!