Allow Modifying sys.user_id Variables Within Workflow Conversation
Self Checks
- [X] I have searched for existing issues search for existing issues, including closed ones.
- [X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
- [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
- [X] Please do not modify this template :) and fill in all the required fields.
1. Is this request related to a challenge you're experiencing? Tell me about your story.
Current Situation
I have integrated Dify into a Web page, and noticed that the workflow automatically generates random sys.user_id values. This makes it difficult for our backend team to identify and track specific users in Dify logs page
Problem
We cannot associate the automatically generated sys.user_id with our actual users in the backend system, which impacts user tracking and analysis.
Feature Request
Is it possible to add functionality that allows us to modify or set custom sys.user_id within the workflow? This would help us:
- Maintain consistent user identification across our systems
- Better track user interactions and behaviors
- Improve user analytics and support capabilities
Use Case
When a user interacts with our Mini Program, we want to use their actual user ID from our system instead of the randomly generated one, ensuring consistent user identification throughout the entire application.
Additional Context
This feature would be particularly valuable for businesses and developers who need to maintain user context across different parts of their applications while using Dify.
2. Additional context or comments
3. Can you help us with this feature?
- [ ] I am interested in contributing to this feature.
@LQ645218172 Have you solved this problem now? I also encountered this problem, it's too distressing
Hi, @LQ645218172. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.
Issue Summary:
- You requested a feature to set custom
sys.user_idvalues for consistent user identification. - The current system's random values complicate user tracking.
- Another user, @jinec, also expressed encountering the same issue.
Next Steps:
- Please let me know if this issue is still relevant to the latest version of Dify by commenting here.
- If there is no further activity, this issue will be automatically closed in 15 days.
Thank you for your understanding and contribution!