-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
environment variable is null when execute node #10065
Comments
The issue you're experiencing, where environment variables are null when executing a node individually in version 0.10.2, might be related to how the In the Dify codebase, the To address this issue, you might want to check if the environment variables are being correctly passed to the |
this bug still exists |
@takatost, the user Qiuzg has indicated that the bug still exists despite the issue being marked stale and closed. Could you please assist them with this? |
Self Checks
Dify version
0.10.2
Cloud or Self Hosted
Self Hosted (Docker), Self Hosted (Source)
Steps to reproduce
In version 0.10.2, when executing a node individually, if the node requires the use of environment variables, the input value obtained for the environment variable is none. However, when the entire process is executed, the environment variables can be obtained. This issue did not exist in version 0.9.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered: