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

Publishing new conversation variables cannot be assigned #10959

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

Originally created by @xjm-studio on GitHub (Mar 13, 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

0.15.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Reproduction Steps:

  1. Publish a chatflow using environment variables.
  2. Add two new environment variables to the production data.
  3. Assign the new variables in the flow.
  4. Error occurs: Variable ['conversation', 'xxxx'] not found.

Issue Description:
We have a conversation in use with over 400 active users. After deploying the changes, the production environment encountered errors.

Questions:
How can we modify the setup to properly use the new environment variables?
Is it necessary to migrate the data from the old conversation to a new conversation? If so, what is the recommended approach?

Image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @xjm-studio on GitHub (Mar 13, 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 0.15.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Reproduction Steps: 1. Publish a chatflow using environment variables. 2. Add two new environment variables to the production data. 3. Assign the new variables in the flow. 4. Error occurs: Variable ['conversation', 'xxxx'] not found. Issue Description: We have a conversation in use with over 400 active users. After deploying the changes, the production environment encountered errors. Questions: How can we modify the setup to properly use the new environment variables? Is it necessary to migrate the data from the old conversation to a new conversation? If so, what is the recommended approach? ![Image](https://github.com/user-attachments/assets/b32e3d5c-6511-416b-8541-aaebc9bf99bc) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:53:14 -05:00
yindo closed this issue 2026-02-21 18:53:14 -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#10959
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?