Variable is unavailable in workflow. #13386

Closed
opened 2026-02-21 19:11:55 -05:00 by yindo · 7 comments
Owner

Originally created by @tigflanker on GitHub (Apr 26, 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.3.0

Cloud or Self Hosted

Cloud

Steps to reproduce

Variable is unavailable in workflow, both in docker and cloud way.
I have already set up a variable, but i can't assign new value.

cloud:
Image

docker:
Image

✔️ Expected Behavior

No response

Actual Behavior

No response

Originally created by @tigflanker on GitHub (Apr 26, 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.3.0 ### Cloud or Self Hosted Cloud ### Steps to reproduce Variable is unavailable in workflow, both in docker and cloud way. I have already set up a variable, but i can't assign new value. cloud: ![Image](https://github.com/user-attachments/assets/5f28b6e2-141d-4ee6-a77f-5bca36873803) docker: ![Image](https://github.com/user-attachments/assets/e9706af4-b172-4dd1-af68-0b829f8e1950) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🌊 feat:workflow label 2026-02-21 19:11:55 -05:00
yindo closed this issue 2026-02-21 19:11:56 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Apr 26, 2025):

I found some similar discussions that might be relevant to your issue:

  1. After the workflow is compiled into the tool, the output variable cannot get the value, and it can be obtained normally in the tool - This discussion is still open and might provide insights into similar variable issues [1].

  2. There is no session variable in the workflow. When will this feature be available? - This is another open discussion that might be related to your problem [2].

Regarding your issue with variable assignment in Dify version 1.3.0, common causes of variable assignment failures include incorrect configuration of value assignments, unsupported operations for specific variable types, and invalid input values. Ensure that the values being assigned are correctly set in the workflow configuration and that the operations and input types are supported [3].

If you are encountering specific error messages, you might want to check the API container logs in your Docker environment for detailed error messages in JSON format, which can help troubleshoot the issue [4].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Apr 26, 2025): <!-- Answer --> I found some similar discussions that might be relevant to your issue: 1. [After the workflow is compiled into the tool, the output variable cannot get the value, and it can be obtained normally in the tool](https://github.com/langgenius/dify/discussions/18195) - This discussion is still open and might provide insights into similar variable issues <sup>[[1]](https://github.com/langgenius/dify/discussions/18195)</sup>. 2. [There is no session variable in the workflow. When will this feature be available?](https://github.com/langgenius/dify/discussions/9803) - This is another open discussion that might be related to your problem <sup>[[2]](https://github.com/langgenius/dify/discussions/9803)</sup>. Regarding your issue with variable assignment in Dify version 1.3.0, common causes of variable assignment failures include incorrect configuration of value assignments, unsupported operations for specific variable types, and invalid input values. Ensure that the values being assigned are correctly set in the workflow configuration and that the operations and input types are supported <sup>[[3]](https://github.com/langgenius/dify/issues/17029)</sup>. If you are encountering specific error messages, you might want to check the API container logs in your Docker environment for detailed error messages in JSON format, which can help troubleshoot the issue <sup>[[4]](https://github.com/langgenius/dify/issues/18506)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/4f515b84-fb47-4258-9ecd-6dde8ade087a?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/4f515b84-fb47-4258-9ecd-6dde8ade087a?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/4f515b84-fb47-4258-9ecd-6dde8ade087a?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/4f515b84-fb47-4258-9ecd-6dde8ade087a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4f515b84-fb47-4258-9ecd-6dde8ade087a?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/4f515b84-fb47-4258-9ecd-6dde8ade087a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4f515b84-fb47-4258-9ecd-6dde8ade087a?feedback_type=other)</sup>
Author
Owner

@su37sm commented on GitHub (Apr 26, 2025):

what does that means no response?
does your chatflow can not output anything when a variable is setted?

@su37sm commented on GitHub (Apr 26, 2025): what does that means no response? does your chatflow can not output anything when a variable is setted?
Author
Owner

@su37sm commented on GitHub (Apr 26, 2025):

I have a similar problem.you can take a look this.
https://github.com/langgenius/dify/issues/18637

@su37sm commented on GitHub (Apr 26, 2025): I have a similar problem.you can take a look this. https://github.com/langgenius/dify/issues/18637
Author
Owner

@su37sm commented on GitHub (Apr 26, 2025):

if you have variable windows in the APP ,you must in the chatflow not workflow,I am sure you are using the chatflow.

@su37sm commented on GitHub (Apr 26, 2025): if you have variable windows in the APP ,you must in the chatflow not workflow,I am sure you are using the chatflow.
Author
Owner

@koushik16 commented on GitHub (Apr 26, 2025):

I am facing the same issue. Not able to set the variable in any block after defining it globally.

@koushik16 commented on GitHub (Apr 26, 2025): I am facing the same issue. Not able to set the variable in any block after defining it globally.
Author
Owner

@tigflanker commented on GitHub (Apr 26, 2025):

if you have variable windows in the APP ,you must in the chatflow not workflow,I am sure you are using the chatflow.

@su37sm No, in fact, I am using the workflow mode precisely. The reason is that my application scenario requires the use of a loop node within the workflow, and the criterion for determining whether to break the loop is to check if a certain variable meets the condition.

In Docker version 1.2.0 and the official documentation, it is indeed the case that variables are not available by default in workflows. I noticed that version 1.3.0 suddenly introduced them, but they cannot be assigned values.

@tigflanker commented on GitHub (Apr 26, 2025): > if you have variable windows in the APP ,you must in the chatflow not workflow,I am sure you are using the chatflow. @su37sm No, in fact, I am using the workflow mode precisely. The reason is that my application scenario requires the use of a loop node within the workflow, and the criterion for determining whether to break the loop is to check if a certain variable meets the condition. In Docker version 1.2.0 and the official documentation, it is indeed the case that variables are not available by default in workflows. I noticed that version 1.3.0 suddenly introduced them, but they cannot be assigned values.
Author
Owner

@crazywoola commented on GitHub (Apr 26, 2025):

It's a frontend bug, and it has been fixed already.

fix: not render conversation var in prompt editor (https://github.com/langgenius/dify/pull/18728)

@crazywoola commented on GitHub (Apr 26, 2025): It's a frontend bug, and it has been fixed already. > fix: not render conversation var in prompt editor (https://github.com/langgenius/dify/pull/18728)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#13386