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

the nodes in the Loop cannot be tracked #11819

New Issue
Closed
opened 2026-02-21 19:04:13 -05:00 by yindo · 9 comments
yindo commented 2026-02-21 19:04:13 -05:00
Owner
Copy Link
Copy Source

Originally created by @zhiyzheng on GitHub (Mar 19, 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

1.0.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The steps progress in the loop cannot be tracked and monitored.
As shown in pic:

Image

✔️ Expected Behavior

Expect it can be tracked step by step

❌ Actual Behavior

No response

Originally created by @zhiyzheng on GitHub (Mar 19, 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 1.0.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The steps progress in the loop cannot be tracked and monitored. As shown in pic: ![Image](https://github.com/user-attachments/assets/b7af8730-f2bd-492c-99cc-aff5e74520b7) ### ✔️ Expected Behavior Expect it can be tracked step by step ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:04:13 -05:00
yindo closed this issue 2026-02-21 19:04:13 -05:00
yindo commented 2026-02-21 19:04:13 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 19, 2025):

Dify has several mechanisms for tracking and monitoring nodes within a loop in a workflow. These include events for loop execution, variable pool management, condition checking, error handling, and metadata handling. These mechanisms collectively help in monitoring the execution flow and state of nodes within a loop [1].

If you're experiencing issues with tracking loop operations in a self-hosted Docker environment, ensure that the environment variable LOOP_NODE_MAX_COUNT is set appropriately, as it controls the maximum loop count [2]. If the problem persists, it might be worth checking if there are any specific configurations or customizations needed for your setup.

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 (Mar 19, 2025): <!-- Answer --> Dify has several mechanisms for tracking and monitoring nodes within a loop in a workflow. These include events for loop execution, variable pool management, condition checking, error handling, and metadata handling. These mechanisms collectively help in monitoring the execution flow and state of nodes within a loop <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/core/workflow/nodes/loop/loop_node.py)</sup>. If you're experiencing issues with tracking loop operations in a self-hosted Docker environment, ensure that the environment variable `LOOP_NODE_MAX_COUNT` is set appropriately, as it controls the maximum loop count <sup>[[2]](https://github.com/langgenius/dify/blob/ac80c04bd34344468b03f9c9e9d68fc7c00a6877/docker/.env.example)</sup>. If the problem persists, it might be worth checking if there are any specific configurations or customizations needed for your setup. <!-- 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/89ca3b0d-0ca6-4cdd-aec7-2340a1a0c57d?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/89ca3b0d-0ca6-4cdd-aec7-2340a1a0c57d?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/89ca3b0d-0ca6-4cdd-aec7-2340a1a0c57d?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/89ca3b0d-0ca6-4cdd-aec7-2340a1a0c57d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/89ca3b0d-0ca6-4cdd-aec7-2340a1a0c57d?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/89ca3b0d-0ca6-4cdd-aec7-2340a1a0c57d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/89ca3b0d-0ca6-4cdd-aec7-2340a1a0c57d?feedback_type=other)</sup>
yindo commented 2026-02-21 19:04:14 -05:00
Author
Owner
Copy Link
Copy Source

@zhiyzheng commented on GitHub (Mar 19, 2025):

@dosu the LOOP_NODE_MAX_COUNT is set as 100, but in my workflow the loop limit is just 3. I don't think it is the root cause.

@zhiyzheng commented on GitHub (Mar 19, 2025): @dosu the LOOP_NODE_MAX_COUNT is set as 100, but in my workflow the loop limit is just 3. I don't think it is the root cause.
yindo commented 2026-02-21 19:04:14 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 19, 2025):

The issue might not be related to the LOOP_NODE_MAX_COUNT setting, especially since your loop limit is well within the allowed range. Instead, the problem could be due to validation issues in the checkValid function. Here are some potential causes:

  1. Break Conditions: Ensure that all break conditions in your loop are correctly configured. Each break condition must have a variable_selector, comparison_operator, and a required value. Missing any of these can cause the loop to be invalid.

  2. Loop Count Validation: Verify that the loop count is a valid integer and falls within the range of 1 to LOOP_NODE_MAX_COUNT. Although your loop limit is 3, any misconfiguration here could still affect tracking.

  3. Sub-variable Conditions: If you have any sub_variable_condition within a break condition, ensure that they are properly set. If the comparison_operator is not empty or notEmpty, all sub-conditions must have a comparison_operator and a value if required by the operator.

Double-check these configurations to ensure that all conditions are met for proper loop tracking [1][2].

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 (Mar 19, 2025): <!-- Answer --> The issue might not be related to the `LOOP_NODE_MAX_COUNT` setting, especially since your loop limit is well within the allowed range. Instead, the problem could be due to validation issues in the `checkValid` function. Here are some potential causes: 1. **Break Conditions**: Ensure that all break conditions in your loop are correctly configured. Each break condition must have a `variable_selector`, `comparison_operator`, and a required `value`. Missing any of these can cause the loop to be invalid. 2. **Loop Count Validation**: Verify that the loop count is a valid integer and falls within the range of 1 to `LOOP_NODE_MAX_COUNT`. Although your loop limit is 3, any misconfiguration here could still affect tracking. 3. **Sub-variable Conditions**: If you have any `sub_variable_condition` within a break condition, ensure that they are properly set. If the `comparison_operator` is not `empty` or `notEmpty`, all sub-conditions must have a `comparison_operator` and a `value` if required by the operator. Double-check these configurations to ensure that all conditions are met for proper loop tracking <sup>[[1]](https://github.com/langgenius/dify/blob/223ab5a38fed5c7c99e1350ff509b62dcf7955ad/web/app/components/workflow/nodes/loop/default.ts#L49-L89)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/106169ed7fbf63eadd2ce560b94ece0b9b84492b/web/app/components/workflow/nodes/loop/default.ts#L49-L89)</sup>. <!-- 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/dfd45b2f-eb97-4117-9631-b78c054811b4?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/dfd45b2f-eb97-4117-9631-b78c054811b4?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/dfd45b2f-eb97-4117-9631-b78c054811b4?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/dfd45b2f-eb97-4117-9631-b78c054811b4?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/dfd45b2f-eb97-4117-9631-b78c054811b4?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/dfd45b2f-eb97-4117-9631-b78c054811b4?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/dfd45b2f-eb97-4117-9631-b78c054811b4?feedback_type=other)</sup>
yindo commented 2026-02-21 19:04:14 -05:00
Author
Owner
Copy Link
Copy Source

@zhiyzheng commented on GitHub (Mar 19, 2025):

@dosu I don't think the issue is due to what you mentioned above. I set several nodes in the loop, and when the whole whole workflow ended, I could not unfold the loop to see the detailed input and output as I show in the screen previously. Maybe you can advise your expertise to help. Thx

@zhiyzheng commented on GitHub (Mar 19, 2025): @dosu I don't think the issue is due to what you mentioned above. I set several nodes in the loop, and when the whole whole workflow ended, I could not unfold the loop to see the detailed input and output as I show in the screen previously. Maybe you can advise your expertise to help. Thx
yindo commented 2026-02-21 19:04:14 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 19, 2025):

Could you provide more details about the setup of your nodes within the loop? Specifically, information about the types of nodes, their configurations, and any specific settings related to input and output handling would be helpful. Additionally, if there are any error messages or logs generated during the workflow execution, sharing those could provide more insight into the issue.

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 (Mar 19, 2025): <!-- Answer --> Could you provide more details about the setup of your nodes within the loop? Specifically, information about the types of nodes, their configurations, and any specific settings related to input and output handling would be helpful. Additionally, if there are any error messages or logs generated during the workflow execution, sharing those could provide more insight into the issue. <!-- 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/e3299bc6-01cc-4624-a98b-5ef63baa446a?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/e3299bc6-01cc-4624-a98b-5ef63baa446a?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/e3299bc6-01cc-4624-a98b-5ef63baa446a?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/e3299bc6-01cc-4624-a98b-5ef63baa446a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e3299bc6-01cc-4624-a98b-5ef63baa446a?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/e3299bc6-01cc-4624-a98b-5ef63baa446a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e3299bc6-01cc-4624-a98b-5ef63baa446a?feedback_type=other)</sup>
yindo commented 2026-02-21 19:04:14 -05:00
Author
Owner
Copy Link
Copy Source

@zhiyzheng commented on GitHub (Mar 19, 2025):

the loop contains these nodes as described in screen shot

Image

And the loop setting for your information

Image

@zhiyzheng commented on GitHub (Mar 19, 2025): the loop contains these nodes as described in screen shot ![Image](https://github.com/user-attachments/assets/ccaee6ed-faf2-40d7-9b1c-321dcda0a43f) And the loop setting for your information ![Image](https://github.com/user-attachments/assets/5ea29de6-14a8-4a30-a09f-e4efc0a963c0)
yindo commented 2026-02-21 19:04:14 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Mar 20, 2025):

Maybe @Woo0ood the author of that node, can help

@DavideDelbianco commented on GitHub (Mar 20, 2025): Maybe @Woo0ood the author of that node, can help
yindo commented 2026-02-21 19:04:14 -05:00
Author
Owner
Copy Link
Copy Source

@Woo0ood commented on GitHub (Mar 20, 2025):

Hi, could you be able to export the DSL for me to reproduce and fix the bug or create a minimal workflow and export its DSL? btw, could you help test whether the same issue occurs in the iteration node? thx~

@Woo0ood commented on GitHub (Mar 20, 2025): Hi, could you be able to export the DSL for me to reproduce and fix the bug or create a minimal workflow and export its DSL? btw, could you help test whether the same issue occurs in the iteration node? thx~
yindo commented 2026-02-21 19:04:14 -05:00
Author
Owner
Copy Link
Copy Source

@zhiyzheng commented on GitHub (Mar 27, 2025):

I already give up the attempt of the loop, so I cannot provide now.

@zhiyzheng commented on GitHub (Mar 27, 2025): I already give up the attempt of the loop, so I cannot provide now.
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#11819
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?