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

In the iteration nodes within a workflow, if a node fails and retries, there will be a retry node that remains in a running state. #8068

New Issue
Closed
opened 2026-02-21 18:23:44 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 18:23:44 -05:00
Owner
Copy Link
Copy Source

Originally created by @wangiii on GitHub (Feb 7, 2025).

Originally assigned to: @laipz8200, @Nov1c444 on GitHub.

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

0.15.3

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

Image

✔️ Expected Behavior

The node that retries should show success instead of adding a node that is always in a running state.

❌ Actual Behavior

The node that needs to be retried has been in a running state.

Originally created by @wangiii on GitHub (Feb 7, 2025). Originally assigned to: @laipz8200, @Nov1c444 on GitHub. ### 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 0.15.3 ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce <img width="1756" alt="Image" src="https://github.com/user-attachments/assets/23c38f25-f63f-4f0c-9a14-f05f786fb6bd" /> ### ✔️ Expected Behavior The node that retries should show success instead of adding a node that is always in a running state. ### ❌ Actual Behavior The node that needs to be retried has been in a running state.
yindo added the 🐞 bug🌊 feat:workflow labels 2026-02-21 18:23:44 -05:00
yindo closed this issue 2026-02-21 18:23:44 -05:00
yindo commented 2026-02-21 18:23:44 -05:00
Author
Owner
Copy Link
Copy Source

@wangiii commented on GitHub (Feb 7, 2025):

验证迭代问题.yml.zip
Reproducible dsl

@wangiii commented on GitHub (Feb 7, 2025): [验证迭代问题.yml.zip](https://github.com/user-attachments/files/18716831/yml.zip) Reproducible dsl
yindo commented 2026-02-21 18:23:44 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 7, 2025):

The issue you're experiencing with iteration nodes remaining in a running state after retries could be related to the specific conditions under which a retry node remains active. In Dify workflows, a retry node remains in a running state when data._runningStatus is equal to NodeRunningStatus.Running and the node is not selected, bundled, or entering, as indicated by the absence of showSelectedBorder [1].

To address this, you might want to check the configuration of your retry nodes and ensure that the conditions for transitioning from a running state to a completed state are correctly set. Additionally, verify that the retry settings, such as max_retries and retry_interval, are appropriately configured to handle node failures and retries effectively [2][3].

If the issue persists, reviewing the specific implementation details in your workflow or consulting the Dify documentation for any updates or patches related to version 0.15.3 might be helpful.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Feb 7, 2025): <!-- Answer --> The issue you're experiencing with iteration nodes remaining in a running state after retries could be related to the specific conditions under which a retry node remains active. In Dify workflows, a retry node remains in a running state when `data._runningStatus` is equal to `NodeRunningStatus.Running` and the node is not selected, bundled, or entering, as indicated by the absence of `showSelectedBorder` <sup>[[1]](https://github.com/langgenius/dify/blob/main/web/app/components/workflow/nodes/_base/components/retry/retry-on-node.tsx)</sup>. To address this, you might want to check the configuration of your retry nodes and ensure that the conditions for transitioning from a running state to a completed state are correctly set. Additionally, verify that the retry settings, such as `max_retries` and `retry_interval`, are appropriately configured to handle node failures and retries effectively <sup>[[2]](https://github.com/langgenius/dify/blob/main/web/app/components/workflow/nodes/_base/components/retry/types.ts)</sup><sup>[[3]](https://github.com/langgenius/dify/blob/main/api/core/workflow/nodes/base/node.py)</sup>. If the issue persists, reviewing the specific implementation details in your workflow or consulting the Dify documentation for any updates or patches related to version 0.15.3 might be helpful. <!-- 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/eb624363-06b1-416c-9d82-0bbc66fcee62?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/eb624363-06b1-416c-9d82-0bbc66fcee62?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/eb624363-06b1-416c-9d82-0bbc66fcee62?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/eb624363-06b1-416c-9d82-0bbc66fcee62?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/eb624363-06b1-416c-9d82-0bbc66fcee62?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/eb624363-06b1-416c-9d82-0bbc66fcee62?feedback_type=other)</sup>
yindo commented 2026-02-21 18:23:44 -05:00
Author
Owner
Copy Link
Copy Source

@wangiii commented on GitHub (Feb 7, 2025):

If the iteration contains an llm node, it returns an empty string when the retry is successful.

Image
@wangiii commented on GitHub (Feb 7, 2025): If the iteration contains an llm node, it returns an empty string when the retry is successful. <img width="1418" alt="Image" src="https://github.com/user-attachments/assets/98523ae5-8eb1-4943-8b73-156c27d1a55f" />
yindo commented 2026-02-21 18:23:45 -05:00
Author
Owner
Copy Link
Copy Source

@ChumyuenLaw commented on GitHub (Feb 9, 2025):

@wangiii I have the same problem. Any updates on this issue?

@ChumyuenLaw commented on GitHub (Feb 9, 2025): @wangiii I have the same problem. Any updates on this issue?
yindo commented 2026-02-21 18:23:45 -05:00
Author
Owner
Copy Link
Copy Source

@wangiii commented on GitHub (Feb 9, 2025):

@wangiii I have the same problem. Any updates on this issue?

Not yet, @laipz8200 watching

@wangiii commented on GitHub (Feb 9, 2025): > [@wangiii](https://github.com/wangiii) I have the same problem. Any updates on this issue? Not yet, @laipz8200 watching
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 🌊 feat:workflow 🐞 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#8068
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?