General Discussion upgrade to 1.8.0, the loop termination condition in loop node does not work

[fangoner]

Self Checks

• 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.

Content

upgrade to 1.8.0, the loop termination condition in loop node does not work

[dosubot[bot]]

Hi @fangoner! I'm Dosu and I’m helping the dify team.

This is a known bug in Dify 1.8.0: the loop node's termination condition does not work properly because variables assigned inside the loop weren't available for the exit condition check. The issue has been fixed in recent updates—specifically, the loop node now checks break conditions only at the end of each loop and correctly uses variables from inside the loop for termination checks. If no variables for the break conditions are available, the loop will break by default to prevent infinite loops. To resolve this, update to the latest version of Dify that includes these fixes (details, PR #24257).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[fangoner]

I update to 1.8.0 only two hours ago, so I should already have all the fixes included. But it is still not work. I have to add condition branch node and exit loop node to realize the function of termination condition. In previous 1.7.2, I can exit the loop anywhere once the some global variables meet termination condition, which is much convenient.

[dosubot[bot]]

The loop termination bug in Dify 1.8.0 was fixed in a recent update, but several important patches for loop node behavior (including proper handling of boolean and non-array segment types) were merged after the initial 1.8.0 release. If you installed 1.8.0 just two hours ago, you may not have these latest fixes yet—upgrading to the newest available version should resolve the issue and restore expected loop termination behavior using variables assigned inside the loop [details, details, details].

If you need to reference global variables for loop termination, the backend supports this if you manually craft the variable selector in the break condition (for example, by editing the workflow JSON directly), but the UI does not expose this capability. For now, your workaround—using a condition branch and exit loop node—is the most reliable method until the UI and documentation catch up with backend capabilities.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[fangoner]

Thank you for clarification. I will wait for next release to update.