@ihaichao Hello! I'm here to help you with any bugs, questions, or contributions while we wait for a human maintainer. Let's work together to solve this issue!

The issue you're experiencing, where edges between nodes inside a copied iteration node are lost, might be related to how the Dify workflow system handles node copying. The function handleNodeIterationChildrenCopy is responsible for copying iteration nodes and their children, but it seems that it might not be preserving the edges between these nodes during the copy process ^[1].

To address this, you might need to ensure that the edges are also copied and re-established when the nodes are duplicated. This could involve modifying the existing functions or adding new logic to handle the preservation of edges when iteration nodes are copied. Unfortunately, the current documentation and codebase do not provide specific details on how edges are managed during the node copying process, so further investigation or code modification might be necessary to resolve this issue.

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}