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

It can't get the inputs params #13248

New Issue
Closed
opened 2026-02-21 19:11:15 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:11:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @liqi0706401043 on GitHub (Apr 23, 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.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

when I request the chat-message api, I want use 'inputs' params to get the databasename, but my server can't get the value of inputs

Image

✔️ Expected Behavior

I want my server can get the params: {
"inputs": {"var":"test"},
"query": "eh",
"response_mode": "streaming",
"conversation_id": "",
"user": "abc-123"
}

❌ Actual Behavior

but I get params:{
"inputs": {},
"query": "eh",
"response_mode": "streaming",
"conversation_id": "",
"user": "abc-123"
}

Image

Originally created by @liqi0706401043 on GitHub (Apr 23, 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.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce when I request the chat-message api, I want use 'inputs' params to get the databasename, but my server can't get the value of inputs ![Image](https://github.com/user-attachments/assets/ee842ad5-30ca-4b76-8c08-1b9a9223fbd0) ### ✔️ Expected Behavior I want my server can get the params: { "inputs": {"var":"test"}, "query": "eh", "response_mode": "streaming", "conversation_id": "", "user": "abc-123" } ### ❌ Actual Behavior but I get params:{ "inputs": {}, "query": "eh", "response_mode": "streaming", "conversation_id": "", "user": "abc-123" } ![Image](https://github.com/user-attachments/assets/192bc12a-9714-4b44-ab69-e2cbe9ddeab1)
yindo added the 🤔 cant-reproduce label 2026-02-21 19:11:15 -05:00
yindo closed this issue 2026-02-21 19:11:15 -05:00
yindo commented 2026-02-21 19:11:16 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 23, 2025):

Hello @liqi0706401043! I'm Dosu, a bot here to help you with bugs, answer questions, and assist you in becoming a contributor. I'm here to support you while you wait for a human maintainer. How can I assist you today?

I found similar threads discussing issues with the 'inputs' parameter in the chat-message API:

  1. In chat-messages, the dialog "inputs:{} cannot be passed in the second time - This discussion is open and suggests ensuring the correct user ID is used in the request to match the one stored in your Dify instance [1].

  2. Ensure the 'inputs' field in /chat-messages takes effect every time - This discussion is also open and highlights similar issues with the 'inputs' field [2].

Additionally, in Dify version 1.2.0, all optional parameters must be explicitly set when making requests to the '/console/api/apps/{app_id}/chat-messages' endpoint. If any optional parameters, including 'inputs', are left blank, it can result in a 500 Internal Server Error [3]. Ensure that you explicitly set all optional parameters with values in your request.

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 (Apr 23, 2025): <!-- Greeting --> Hello @liqi0706401043! I'm [Dosu](https://dosu.dev), a bot here to help you with bugs, answer questions, and assist you in becoming a contributor. I'm here to support you while you wait for a human maintainer. How can I assist you today? <!-- Answer --> I found similar threads discussing issues with the 'inputs' parameter in the chat-message API: 1. [In chat-messages, the dialog "inputs:{} cannot be passed in the second time](https://github.com/langgenius/dify/discussions/10070) - This discussion is open and suggests ensuring the correct user ID is used in the request to match the one stored in your Dify instance <sup>[[1]](https://github.com/langgenius/dify/discussions/10070)</sup>. 2. [Ensure the 'inputs' field in /chat-messages takes effect every time](https://github.com/langgenius/dify/discussions/10652) - This discussion is also open and highlights similar issues with the 'inputs' field <sup>[[2]](https://github.com/langgenius/dify/discussions/10652)</sup>. Additionally, in Dify version 1.2.0, all optional parameters must be explicitly set when making requests to the '/console/api/apps/{app_id}/chat-messages' endpoint. If any optional parameters, including 'inputs', are left blank, it can result in a 500 Internal Server Error <sup>[[3]](https://github.com/langgenius/dify/issues/17952)</sup>. Ensure that you explicitly set all optional parameters with values in your request. <!-- 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/b70d60ea-d499-4457-90c2-88733894979a?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b70d60ea-d499-4457-90c2-88733894979a?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b70d60ea-d499-4457-90c2-88733894979a?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b70d60ea-d499-4457-90c2-88733894979a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b70d60ea-d499-4457-90c2-88733894979a?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/b70d60ea-d499-4457-90c2-88733894979a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b70d60ea-d499-4457-90c2-88733894979a?feedback_type=other)</sup>
yindo commented 2026-02-21 19:11:16 -05:00
Author
Owner
Copy Link
Copy Source

@liqi0706401043 commented on GitHub (Apr 23, 2025):

这是来自QQ邮箱的假期自动回复邮件。
 
您好，你的邮件我已收到。

@liqi0706401043 commented on GitHub (Apr 23, 2025): 这是来自QQ邮箱的假期自动回复邮件。   您好，你的邮件我已收到。
yindo commented 2026-02-21 19:11:16 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Apr 23, 2025):

Please provide more details, maybe payload and logs.

@crazywoola commented on GitHub (Apr 23, 2025): Please provide more details, maybe payload and logs.
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 🤔 cant-reproduce
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#13248
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?