the parameters, of chat workflow, cannot be changed in one chat conversation

[memorylorry]

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

none

Cloud or Self Hosted

Cloud

Steps to reproduce

Here is an easy chat workflow, built like this picture. This bug is at the input parameters of workflow.

Firstly, I request chat workflow by postman with the following parameters, as shown in next picture. It is fine.

{
    "conversation_id": "",
    "inputs": {
        "content": "你好啊，content"
    },
    "query": "万科的利润?",
    "response_mode": "streaming",
    "user": "1300000000"
}

Secondly, I request again with conversationId. The parameters is as follow. The problem is occured.

{
    "conversation_id": "a833fb3c-2265-4e92-b78e-7ac1519787e4",
    "inputs": {
        "content": "你好啊，content is not null"
    },
    "query": "你好?",
    "response_mode": "streaming",
    "user": "1300000000"
}

You can nontice it that the parameters of content is the same as the first one call. I think that it must be a bug.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot]

@memorylorry Hello there! I'm here to assist you with any bugs, questions, or contributions you have. Let's work together to resolve your issue.

I found some similar issues and discussions that might be relevant to your problem:

1. Discussion: Why this not work - This discussion is still open and was last updated on September 5, 2024.
2. Issue: Can a variable pool like node (or component) be added to the chat workflow, and any node can access and modify these variable values? - This issue is closed and was last updated on August 21, 2024. It has no comments or solution.
3. Issue: In the same conversation, modifying variables in inputs does not take effect. - This issue is closed and was last updated on September 6, 2024. The suggested solution is to use conversational variables instead. More details can be found here.
4. Issue: Issue with Inputs and variables in chatflow. - This issue is closed and was last updated on July 4, 2024. The suggested solution involves using Dify's built-in features for conversation applications, such as Expert Mode, form variables, and debugging features.

Regarding your specific issue, the parameters of the chat workflow cannot be changed in one chat conversation in Dify because the output variables of nodes are generally fixed variables and cannot be edited. Additionally, once a conversation_id is generated, any new inputs will be ignored in subsequent API calls, and only the query is processed for the ongoing conversation. This ensures the continuity and consistency of the conversation flow ^[1][2].

For more detailed guidance, you might want to refer to the Dify documentation on variable assignment and developing with APIs.

To continue talking to Dosu, mention @dosu.