New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with Inputs and variables in chatflow. #4241
Comments
To address the issue of persisting variables for use in subsequent chat iterations in Dify, and the challenge with input values being ignored in the second message, consider the following approach:
This approach should help overcome the limitations you've encountered with variable persistence and input handling in Dify version 0.6.7. For more detailed guidance on using the
|
@dosu let me know if you understand the problem. |
Yes, I understand the problem. You're facing two main issues: first, input values sent in the second message are being ignored, and second, you're looking for a way to persist variables across chat iterations for future use. The solutions provided aim to address both concerns by suggesting the use of system variables and the
|
@dosu but manage a external storage for a state is a lot of work. |
To streamline the management of input parameters and variable persistence in Dify without the need for external databases, consider leveraging Dify's built-in features for conversation applications. Here's a more focused approach:
For detailed guidance, refer to the Dify documentation and the Prompt Engineering guide. The Node.js client SDK can also provide insights into interacting with Dify's API. This approach should help you manage input parameters and persist variables effectively within your Dify chat applications, streamlining the process and enhancing user interactions.
|
@santiagoblanco22 Can you describe the specific scenario where this feature is required? |
Self Checks
Dify version
0.6.7
Cloud or Self Hosted
Cloud
Steps to reproduce
Try to send params the first time and works.
But If I send the second with the conversationId in the payload for refresh the value, not works.
Other thing, in my opinion is a bad idea:
Variables referenced within a node can only be those from preceding process nodes to ensure coherence and avoid duplication.
Maybe I want to save a variable for a future use in the first node. I don't know how to persist variables for use in the next chat iteration :(
✔️ Expected Behavior
You can send inputs params in all messages and save variables.
❌ Actual Behavior
Ignore the value of the input in the second message.
The text was updated successfully, but these errors were encountered: