langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Failed to call the Zhipu LLM #11868

New Issue
Closed
opened 2026-02-21 19:04:28 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:04:28 -05:00
Owner
Copy Link
Copy Source

Originally created by @hackeryutu on GitHub (Mar 20, 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.1.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Run failed: [zhipuai] Error: PluginInvokeError: {"args":{"description":"[models] Error: Error code: 400, with error text {"error":{"code":"1214","message":"messages 参数非法。请检查文档。"}}"},"error_type":"InvokeError","message":"[models] Error: Error code: 400, with error text {"error":{"code":"1214","message":"messages 参数非法。请检查文档。"}}"}

[zhipuai] Error: PluginInvokeError: {"args":{"description":"[models] Error: Error code: 400, with error text {"error":{"code":"1214","message":"messages 参数非法。请检查文档。"}}"},"error_type":"InvokeError","message":"[models] Error: Error code: 400, with error text {"error":{"code":"1214","message":"messages 参数非法。请检查文档。"}}"}

input:
{
"#context#": "你好"
}

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @hackeryutu on GitHub (Mar 20, 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.1.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Run failed: [zhipuai] Error: PluginInvokeError: {"args":{"description":"[models] Error: Error code: 400, with error text {"error":{"code":"1214","message":"messages 参数非法。请检查文档。"}}"},"error_type":"InvokeError","message":"[models] Error: Error code: 400, with error text {"error":{"code":"1214","message":"messages 参数非法。请检查文档。"}}"} [zhipuai] Error: PluginInvokeError: {"args":{"description":"[models] Error: Error code: 400, with error text {\"error\":{\"code\":\"1214\",\"message\":\"messages 参数非法。请检查文档。\"}}"},"error_type":"InvokeError","message":"[models] Error: Error code: 400, with error text {\"error\":{\"code\":\"1214\",\"message\":\"messages 参数非法。请检查文档。\"}}"} input: { "#context#": "你好" } ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:04:28 -05:00
yindo closed this issue 2026-02-21 19:04:28 -05:00
yindo commented 2026-02-21 19:04:28 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 20, 2025):

@hackeryutu Hello! I'm here to assist you with any bugs, questions, or contributions you have for the project. Let me know how I can help you!

I found a similar unsolved discussion regarding issues with API interface calls and context parsing in Dify [1].

For the error code '1214' and the message "messages 参数非法" (which translates to "messages parameter is illegal"), it suggests that there might be an issue with how the 'messages' parameter is being formatted or used in your API call. Unfortunately, I couldn't find specific documentation on this error code or parameter requirements in the Dify repository.

However, you might want to check the following:

  1. Ensure that the 'messages' parameter is formatted correctly according to the API's requirements. This might involve checking the data type, structure, or any specific fields that need to be included.
  2. Review any available documentation or examples for the Zhipu LLM API to verify the correct usage of the 'messages' parameter.
  3. Consider looking into the Dify documentation's "Troubleshooting Guide" for any general guidance on API call issues [2].

If these steps don't resolve the issue, you might need to explore further discussions or reach out to others who have faced similar issues.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Mar 20, 2025): <!-- Greeting --> @hackeryutu Hello! I'm here to assist you with any bugs, questions, or contributions you have for the project. Let me know how I can help you! <!-- Answer --> I found a similar unsolved discussion regarding issues with API interface calls and context parsing in Dify <sup>[[1]](https://github.com/langgenius/dify/discussions/10044)</sup>. For the error code '1214' and the message "messages 参数非法" (which translates to "messages parameter is illegal"), it suggests that there might be an issue with how the 'messages' parameter is being formatted or used in your API call. Unfortunately, I couldn't find specific documentation on this error code or parameter requirements in the Dify repository. However, you might want to check the following: 1. Ensure that the 'messages' parameter is formatted correctly according to the API's requirements. This might involve checking the data type, structure, or any specific fields that need to be included. 2. Review any available documentation or examples for the Zhipu LLM API to verify the correct usage of the 'messages' parameter. 3. Consider looking into the Dify documentation's "Troubleshooting Guide" for any general guidance on API call issues <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/use-cases/dify-schedule.md)</sup>. If these steps don't resolve the issue, you might need to explore further discussions or reach out to others who have faced similar issues. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/56637cbc-be49-4d0a-a1b4-dc2f8cf986ae?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/56637cbc-be49-4d0a-a1b4-dc2f8cf986ae?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/56637cbc-be49-4d0a-a1b4-dc2f8cf986ae?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/56637cbc-be49-4d0a-a1b4-dc2f8cf986ae?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/56637cbc-be49-4d0a-a1b4-dc2f8cf986ae?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/56637cbc-be49-4d0a-a1b4-dc2f8cf986ae?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/56637cbc-be49-4d0a-a1b4-dc2f8cf986ae?feedback_type=other)</sup>
yindo commented 2026-02-21 19:04:28 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Mar 20, 2025):

Some models in Zhipu only support using user and assistant, you can move those prompts from system instead. Also, this is not a bug of us. You should really check their docs.

@crazywoola commented on GitHub (Mar 20, 2025): Some models in Zhipu only support using `user` and `assistant`, you can move those prompts from `system` instead. Also, this is not a bug of us. You should really check their docs.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#11868
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?