The logic of displaying nodes executed within a iteration node is incorrect

[fdb02983rhy]

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

Cloud or Self Hosted

Cloud

Steps to reproduce

2.yml.zip

✔️ Expected Behavior

They belong to the same iteration

https://github.com/user-attachments/assets/8b622810-718f-4d69-94d4-3fe6d79d0f14

❌ Actual Behavior

https://github.com/user-attachments/assets/9f89fb05-b3df-4a8f-9de3-52cc337c715b

[dosubot[bot]]

The logic for displaying nodes executed within an iteration node in Dify is designed so that the result should not include any nodes within the iteration node itself. This is verified by a test that checks for the absence of nodes with execution_metadata?.iteration_id in the result ^[1]. If you're experiencing issues with this logic, it might be helpful to review the test and ensure that the implementation aligns with this expected behavior.

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]

What's your expected behavior?

[fdb02983rhy]

What's your expected behavior?

Hi, I have updated some more screenshots.

[qkzsky]

I also encountered the same problem where the tracking logs of iterations were not aggregated. This issue occurred in version 1.0.0