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

Unexpected Node Execution Occurs After Final Path Completes in an Iteration, Causing Workflow to Hang #18127

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

Originally created by @v-49 on GitHub (Sep 24, 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

v1.7.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image We have designed a workflow that utilizes an Iteration node. The intended logic within each iteration is that once a specific path of execution is completed and reaches a terminal Answer node, that particular iteration cycle should conclude.

✔️ Expected Behavior

Image

The workflow should complete the current iteration cycle immediately after the designated Answer node has finished executing. It should not re-execute any previous nodes. The process should then either move to the next item in the iteration or exit the loop if all items have been processed.

❌ Actual Behavior

Image During runtime, after the workflow correctly executes the intended path and streams the output from the final Answer node for the current iteration, it unexpectedly triggers a previous node from the workflow again. This re-triggered node appears to be empty or lacks the required input, as it was not part of the planned execution sequence at that stage. This unexpected and invalid step causes the entire workflow to hang indefinitely, preventing it from proceeding to the next iteration or completing successfully.
Originally created by @v-49 on GitHub (Sep 24, 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 v1.7.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="1620" height="463" alt="Image" src="https://github.com/user-attachments/assets/1f55c3e8-5139-46a4-85bc-5dec1c9081bd" /> We have designed a workflow that utilizes an Iteration node. The intended logic within each iteration is that once a specific path of execution is completed and reaches a terminal Answer node, that particular iteration cycle should conclude. ### ✔️ Expected Behavior <img width="566" height="614" alt="Image" src="https://github.com/user-attachments/assets/ff9177df-5324-4cc5-a231-4d96e2a17194" /> The workflow should complete the current iteration cycle immediately after the designated Answer node has finished executing. It should not re-execute any previous nodes. The process should then either move to the next item in the iteration or exit the loop if all items have been processed. ### ❌ Actual Behavior <img width="607" height="1069" alt="Image" src="https://github.com/user-attachments/assets/d71ba4e0-e1c2-4d23-9fd2-f90bf2d6e026" /> During runtime, after the workflow correctly executes the intended path and streams the output from the final Answer node for the current iteration, it unexpectedly triggers a previous node from the workflow again. This re-triggered node appears to be empty or lacks the required input, as it was not part of the planned execution sequence at that stage. This unexpected and invalid step causes the entire workflow to hang indefinitely, preventing it from proceeding to the next iteration or completing successfully.
yindo added the 🐞 bug label 2026-02-21 19:43:53 -05:00
yindo closed this issue 2026-02-21 19:43:53 -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#18127
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?