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

When there are too many branches, the execution of iterative nodes will get stuck #18274

New Issue
Closed
opened 2026-02-21 19:45:42 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 19:45:42 -05:00
Owner
Copy Link
Copy Source

Originally created by @xuesd on GitHub (Sep 26, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.8.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When there are too many branches, the execution of iterative nodes will get stuck
I originally thought it was due to concurrency, the number of workers, and other limitations. After modifying the parameters, it still had no effect until I reduced some branches and the iteration nodes could be used normally

At the same time, I found that sending 30 concurrent requests to API services in the iteration node would result in longer request times. I can confirm that it is not an issue with the API service.

✔️ Expected Behavior

iteration nodes could be used normally

❌ Actual Behavior

No response

Originally created by @xuesd on GitHub (Sep 26, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.8.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When there are too many branches, the execution of iterative nodes will get stuck I originally thought it was due to concurrency, the number of workers, and other limitations. After modifying the parameters, it still had no effect until I reduced some branches and the iteration nodes could be used normally At the same time, I found that sending 30 concurrent requests to API services in the iteration node would result in longer request times. I can confirm that it is not an issue with the API service. ### ✔️ Expected Behavior iteration nodes could be used normally ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:45:42 -05:00
yindo closed this issue 2026-02-21 19:45:42 -05:00
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 🐞 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#18274
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?