You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
In chatflow, Insert an Iteration node , set the output variable "result". You will see that the next node, for example, a LLM node, you can't find that "result" variable in the variable lists.
✔️ Expected Behavior
can access output variable of Iteration node.
❌ Actual Behavior
The Iteration node will not appear in the list of the next node, so you can't find the output variable
The text was updated successfully, but these errors were encountered:
Regarding your issue, the Iteration node in Dify's chatflow is expected to output only array variables (Array[List]). It processes each element in the input array sequentially, and the final output is also in the form of an array. Ensure that the input to the Iteration node is correctly formatted as an array, and check if the output variable is being correctly defined as an array [4].
If the issue persists, it might be related to known bugs or issues in the Dify codebase, such as IteratorVariableNotFoundError or InvalidIteratorValueError, which can affect variable passing between nodes [5].
Self Checks
Dify version
1.01
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
In chatflow, Insert an Iteration node , set the output variable "result". You will see that the next node, for example, a LLM node, you can't find that "result" variable in the variable lists.
✔️ Expected Behavior
can access output variable of Iteration node.
❌ Actual Behavior
The Iteration node will not appear in the list of the next node, so you can't find the output variable
The text was updated successfully, but these errors were encountered: