langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-28 05:20:07 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Most of nodes in the Loop cannot be tracked when there are 4 parallel branches #12661

New Issue
Closed
opened 2026-02-21 19:08:26 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:08:26 -05:00
Owner
Copy Link
Copy Source

Originally created by @JunT-ctrl on GitHub (Apr 8, 2025).

Self Checks

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

Dify version

the nodes in the Loop cannot be tracked

Cloud or Self Hosted

Cloud

Steps to reproduce

Image
The loop layout is shown in the image. When I operate the loop and obtain its result, I can only track the second node of large language mode named Low level skill 2, as shown in the right part of image. In the card named "Test Run#37", there only one parallel node under “循环1"( Loop 1st). But in fact there should be 4 large language modes, which named "Low level skill 1", "Low level skill 2", "High level skill 1" and "High level skill 2"

✔️ Expected Behavior

When we run the loop and obtain its results, we should see the result of all nodes in every single time of looping.

❌ Actual Behavior

we can only see the result of one node

Originally created by @JunT-ctrl on GitHub (Apr 8, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version the nodes in the Loop cannot be tracked ### Cloud or Self Hosted Cloud ### Steps to reproduce ![Image](https://github.com/user-attachments/assets/36194af3-0c57-4b9d-96c6-60a567010626) The loop layout is shown in the image. When I operate the loop and obtain its result, I can only track the second node of large language mode named Low level skill 2, as shown in the right part of image. In the card named "Test Run#37", there only one parallel node under “循环1"( Loop 1st). But in fact there should be 4 large language modes, which named "Low level skill 1", "Low level skill 2", "High level skill 1" and "High level skill 2" ### ✔️ Expected Behavior When we run the loop and obtain its results, we should see the result of all nodes in every single time of looping. ### ❌ Actual Behavior we can only see the result of one node
yindo added the 🐞 bugcloud labels 2026-02-21 19:08:26 -05:00
yindo closed this issue 2026-02-21 19:08:26 -05:00
yindo commented 2026-02-21 19:08:26 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 8, 2025):

嗨 @JunT-ctrl！我是一个可以帮助你解决bug、回答问题并成为贡献者的机器人。在你等待人类维护者的同时，我会尽力帮助你！🤖

The issue you're experiencing with tracking nodes in parallel branches within loops in Dify might be related to specific configurations or limitations in the system. Here are a few points to consider:

  1. Parallel Execution Configuration: Ensure that the is_parallel setting in the IterationNode configuration is correctly set to allow parallel execution. This setting determines whether nodes in the iteration should run in parallel branches [1].

  2. Logging and Visibility: Dify's logging mechanism should ideally track the execution of all nodes, including those in parallel branches. However, there might be limitations or bugs affecting the visibility of these nodes in the UI. This could be a reason why only one node's result is visible.

  3. Error Handling: If there are errors or exceptions occurring in the parallel branches, they might be affecting the visibility of node results. Dify uses specific event entities to handle and report errors in parallel branches [2].

Given these points, you might want to check the configuration settings and ensure that error handling mechanisms are properly set up. If the issue persists, it could be a bug that needs further investigation by the development team.

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

@dosubot[bot] commented on GitHub (Apr 8, 2025): <!-- Greeting --> 嗨 @JunT-ctrl！我是一个可以帮助你解决bug、回答问题并成为贡献者的机器人。在你等待人类维护者的同时，我会尽力帮助你！🤖 <!-- Answer --> The issue you're experiencing with tracking nodes in parallel branches within loops in Dify might be related to specific configurations or limitations in the system. Here are a few points to consider: 1. **Parallel Execution Configuration**: Ensure that the `is_parallel` setting in the `IterationNode` configuration is correctly set to allow parallel execution. This setting determines whether nodes in the iteration should run in parallel branches <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/workflow/nodes/iteration/iteration_node.py)</sup>. 2. **Logging and Visibility**: Dify's logging mechanism should ideally track the execution of all nodes, including those in parallel branches. However, there might be limitations or bugs affecting the visibility of these nodes in the UI. This could be a reason why only one node's result is visible. 3. **Error Handling**: If there are errors or exceptions occurring in the parallel branches, they might be affecting the visibility of node results. Dify uses specific event entities to handle and report errors in parallel branches <sup>[[2]](https://github.com/langgenius/dify/blob/main/api/core/app/entities/queue_entities.py)</sup>. Given these points, you might want to check the configuration settings and ensure that error handling mechanisms are properly set up. If the issue persists, it could be a bug that needs further investigation by the development team. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/7e5d7e94-7820-4c3f-b053-e5fb5339191b?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/7e5d7e94-7820-4c3f-b053-e5fb5339191b?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/7e5d7e94-7820-4c3f-b053-e5fb5339191b?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/7e5d7e94-7820-4c3f-b053-e5fb5339191b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7e5d7e94-7820-4c3f-b053-e5fb5339191b?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/7e5d7e94-7820-4c3f-b053-e5fb5339191b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7e5d7e94-7820-4c3f-b053-e5fb5339191b?feedback_type=other)</sup>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label cloud 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#12661
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?