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

request inputs args invalid #8130

New Issue
Closed
opened 2026-02-21 18:24:06 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:24:06 -05:00
Owner
Copy Link
Copy Source

Originally created by @ENCHIGO on GitHub (Feb 10, 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

v0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Pass in custom parameters when continuing the conversation

Image Image

✔️ Expected Behavior

i hope that whether it is the first time to create a conversation or continue this conversation, the custom input parameters will be effective.

❌ Actual Behavior

Customized parameters only take effect when creating a conversation, and have no effect when continuing the conversation content.

Originally created by @ENCHIGO on GitHub (Feb 10, 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 v0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Pass in custom parameters when continuing the conversation <img width="428" alt="Image" src="https://github.com/user-attachments/assets/97e4d697-ff76-49e0-b121-1d717742bff8" /> <img width="445" alt="Image" src="https://github.com/user-attachments/assets/17b8e0fb-b86d-40e1-a2cd-9400fb6952f6" /> ### ✔️ Expected Behavior i hope that whether it is the first time to create a conversation or continue this conversation, the custom input parameters will be effective. ### ❌ Actual Behavior Customized parameters only take effect when creating a conversation, and have no effect when continuing the conversation content.
yindo added the 🐞 bug label 2026-02-21 18:24:06 -05:00
yindo closed this issue 2026-02-21 18:24:06 -05:00
yindo commented 2026-02-21 18:24:06 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 10, 2025):

@ENCHIGO Hello! I'm here to help you with bugs, questions, and becoming a contributor. Let's work on solving the issue together while we wait for a human maintainer.

I found some relevant information regarding the issue you're experiencing with the 'inputs' field in continued conversations.

  1. When continuing an existing conversation using the Dify API, any new inputs will be ignored if a previous conversation_id is passed. Only the query is processed for the ongoing conversation. This is intended to maintain the continuity of the conversation with the Dify bot [1].

  2. There are similar discussions on this topic:

The current behavior is by design, where inputs are only processed when creating a new conversation. If you need to adjust the bot's behavior during a session, consider using conversation-specific variables to manage dynamic changes.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 10, 2025): <!-- Greeting --> @ENCHIGO Hello! I'm here to help you with bugs, questions, and becoming a contributor. Let's work on solving the issue together while we wait for a human maintainer. <!-- Answer --> I found some relevant information regarding the issue you're experiencing with the 'inputs' field in continued conversations. 1. When continuing an existing conversation using the Dify API, any new `inputs` will be ignored if a previous `conversation_id` is passed. Only the `query` is processed for the ongoing conversation. This is intended to maintain the continuity of the conversation with the Dify bot <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/application-publishing/developing-with-apis.md)</sup>. 2. There are similar discussions on this topic: - [Ensure the 'inputs' field in /chat-messages takes effect every time](https://github.com/langgenius/dify/discussions/10652) - This discussion is unsolved and might provide additional context. - [The inputs of the conversation is can not be modified after the conversation created?](https://github.com/langgenius/dify/discussions/12259) - Another unsolved discussion that might be relevant. - [In chat-messages, the dialog "inputs:{} cannot be passed in the second time](https://github.com/langgenius/dify/discussions/10070) - This is also unsolved and could offer more insights. The current behavior is by design, where `inputs` are only processed when creating a new conversation. If you need to adjust the bot's behavior during a session, consider using conversation-specific variables to manage dynamic changes. <!-- 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/ba6642b1-b5f2-4173-b699-b5c3c84000ca?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ba6642b1-b5f2-4173-b699-b5c3c84000ca?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ba6642b1-b5f2-4173-b699-b5c3c84000ca?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ba6642b1-b5f2-4173-b699-b5c3c84000ca?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ba6642b1-b5f2-4173-b699-b5c3c84000ca?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/ba6642b1-b5f2-4173-b699-b5c3c84000ca?feedback_type=other)</sup>
yindo commented 2026-02-21 18:24:06 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 10, 2025):

Duplicated

@crazywoola commented on GitHub (Feb 10, 2025): Duplicated
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#8130
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?