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

All newly created session variables in v1.01 are invalid in the API #11242

New Issue
Closed
opened 2026-02-21 18:57:19 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 18:57:19 -05:00
Owner
Copy Link
Copy Source

Originally created by @shuker2024 on GitHub (Mar 16, 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

1.01

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Issue Description: New Session variables Fail in API Calls After Upgrade
After upgrading to version 1.01, newly created Session variables are invalid in API-triggered executions, while session variables preserved before the upgrade function normally. Specifically:
In the web interface, [Variable Assignment] nodes correctly read/override new Session variables.
In API-invoked workflows, [Variable Assignment] nodes throw errors like Variable ['conversation', 'XX'] not found for the same variables.
Reproduction Steps
1.Create a new chatflow app.
2.Define a session variable XX.
3.Add an LLM node (any prompt).
4.Add a [Variable Assignment] node to assign the LLM output to the session variable XX.
5.Add a Direct Reply node.
· Web test: Works normally.
· API test (with an API key): Fails with Variable ['conversation', 'XX'] not found.
Key Point: The error only occurs when triggering the chatflow via external API calls, not in the web-based test.
Error Snippet
Variable ['conversation', 'XX'] not found # Observed in API-triggered executions
Note: It is about session variables, not environment variables!
Let me know if further technical details are needed!

✔️ Expected Behavior

Hope it's resolved。

❌ Actual Behavior

No response

Originally created by @shuker2024 on GitHub (Mar 16, 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 1.01 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Issue Description: New Session variables Fail in API Calls After Upgrade After upgrading to version 1.01, newly created Session variables are invalid in API-triggered executions, while session variables preserved before the upgrade function normally. Specifically: In the web interface, [Variable Assignment] nodes correctly read/override new Session variables. In API-invoked workflows, [Variable Assignment] nodes throw errors like Variable ['conversation', 'XX'] not found for the same variables. Reproduction Steps 1.Create a new chatflow app. 2.Define a session variable XX. 3.Add an LLM node (any prompt). 4.Add a [Variable Assignment] node to assign the LLM output to the session variable XX. 5.Add a Direct Reply node. · Web test: Works normally. · API test (with an API key): Fails with Variable ['conversation', 'XX'] not found. Key Point: The error only occurs when triggering the chatflow via external API calls, not in the web-based test. Error Snippet `Variable ['conversation', 'XX'] not found # Observed in API-triggered executions` **Note: It is about session variables, not environment variables!** Let me know if further technical details are needed! ### ✔️ Expected Behavior Hope it's resolved。 ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:57:19 -05:00
yindo closed this issue 2026-02-21 18:57:19 -05:00
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#11242
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?