maybe it is a bug for the chatflow--second time

[su37sm]

Self Checks

• [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [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.

Dify version

1.3.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Dear Dify Team,​​ This is my second submission regarding a suspected bug in ChatFlow. Yesterday, I submitted a report, but it was closed. ​​Please take the time to carefully read through my description:​​

For context, this issue involves the ​​ChatFlow application on Dify v1.3.0​​. Why am I submitting this again? Because I completely reset my server’s hard drive, reformatted everything, reinstalled Docker, and pulled a fresh copy of Dify v1.3.0 with entirely new data. ​​No residual configurations or data remain.​​

After launching the ChatFlow application, I configured a variable named ​​tst​​ with a default value. When I attempted to preview the workflow, ​​no output was generated​​ — the execution simply stalled. However, ​​when I removed this variable​​, the preview functioned normally and produced output.

The behavior and logs are fundamentally identical to what I reported yesterday. However, since my environment is now ​​completely clean and interference-free​​, I’ve reproduced the issue under pristine conditions. This leads me to believe this is a ​​potential bug in Dify​​. I kindly request your team to investigate this further.

Thank you for your attention and support.

0423log.txt

✔️ Expected Behavior

chatflow can work well as usual

❌ Actual Behavior

chatflow can not work at all

[dosubot[bot]]

There is a known issue in the Dify repository related to variable handling in the ChatFlow application. In Dify v0.15.3, a similar problem was reported where the flow gets stuck at a specific node when certain configurations are used. Although this was noted in a previous version, it might be related to your current issue in v1.3.0. The problem was associated with a parallel chatflow involving a Question Classifier node connected to a Variable Assigner and If/Else node. The workaround was to remove the connection between the Variable Assigner and If/Else node to resolve the issue ^[1].

Given your description, it seems that the variable tst might be causing a similar issue. You might want to check if there are any specific nodes or configurations in your workflow that could be interacting with this variable in a way that causes the execution to stall. Additionally, reviewing the logs for any error messages related to variable handling could provide more insights.

If the issue persists, consider testing with different configurations or simplifying the workflow to isolate the problem further.

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}

[crazywoola]

Sorry, I can not reproduce this error. I have performed a clean install as well. Maybe you should provide more information regarding the machine's arch.

[laipz8200]

Can you export and upload your DSL file? It seems like you have a conversation variable with the wrong ID.

[su37sm]

1.zip

Can you export and upload your DSL file? It seems like you have a conversation variable with the wrong ID.

here is the DSL file.

[su37sm]

Sorry, I can not reproduce this error. I have performed a clean install as well. Maybe you should provide more information regarding the machine's arch.

system info:Ubuntu 22.04.4 LTS Docker version 28.1.1, build 4eba377 Docker Compose version v2.35.1

I have only installed docker and docker compose and dify V1.3.0

[su37sm]

pic1 :none variable,work well as usual pic2:add a variable named text pic3:preview can not output

[su37sm]

Sorry, I can not reproduce this error. I have performed a clean install as well. Maybe you should provide more information regarding the machine's arch.

I buy another cloud server,and do the same processes,also have the same issues. Ubuntu 24.04 LTS Docker version 28.1.1, build 4eba377 Docker Compose version v2.35.1

[su37sm]

@laipz8200 @crazywoola would you please leave a Email,I will send the server 's info so that you can log in the server and find out what happened.

[su37sm]

Sorry, I can not reproduce this error. I have performed a clean install as well. Maybe you should provide more information regarding the machine's arch.

would you mind to tell me your server‘s configuration? I have four servers with ubuntu the same issues.

[su37sm]

@crazywoola hello,please pay attendation for this. I do test in windows docker desktop,find that it is very peace when I add an variable and nothing goes wrong.yes,I think ubuntu+docker+docker compose could cause something abnormal.

[crazywoola]

@laipz8200 @crazywoola would you please leave a Email,I will send the server 's info so that you can log in the server and find out what happened.

[email protected] @su37sm

[dosubot[bot]]

Hi, @su37sm. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

• You reported a persistent bug in Dify v1.3.0 where adding a variable with a default value in ChatFlow causes the workflow preview to stall without output.
• The issue occurs on multiple Ubuntu servers despite clean reinstalls, but not on Windows Docker Desktop, suggesting a possible Ubuntu+Docker interaction.
• Contributors referenced a similar known issue in earlier versions and requested environment details and the DSL file, which you provided.
• Other maintainers have been unable to reproduce the problem and have not identified a clear resolution.
• You have offered server access for deeper investigation, but no further progress has been reported.

Next Steps:

• Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
• Otherwise, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!