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

The log in the loop node shows abnormality #13602

New Issue
Closed
opened 2026-02-21 19:12:56 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 19:12:56 -05:00
Owner
Copy Link
Copy Source

Originally created by @auxpd on GitHub (May 2, 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.3.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

This is my workflow in the loop:

Image

This is the log output:

Image

As long as there is parallelism in the loop, log loss will occur.

✔️ Expected Behavior

All nodes can be rendered correctly

❌ Actual Behavior

node log lost

Originally created by @auxpd on GitHub (May 2, 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.3.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce This is my workflow in the loop: <img width="683" alt="Image" src="https://github.com/user-attachments/assets/d900fc1c-139a-431f-a9c2-98edf0ef8f11" /> This is the log output: <img width="307" alt="Image" src="https://github.com/user-attachments/assets/1ed66fc9-fbe8-4f6f-8c95-537edc7a5e31" /> As long as there is parallelism in the loop, log loss will occur. ### ✔️ Expected Behavior All nodes can be rendered correctly ### ❌ Actual Behavior node log lost
yindo closed this issue 2026-02-21 19:12:56 -05:00
yindo commented 2026-02-21 19:12:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 2, 2025):

There is a known issue in Dify version 1.0.1 where not all parallel node executions are fully displayed in the workflow logs when using Iteration or Parallel nodes. This issue has been fixed in a later version through pull request #14855. Since you are using version 1.3.1, this specific issue should not be present. However, if you are experiencing similar log loss, it might be worth checking your logging configurations and settings related to parallelism.

Additionally, you might want to review the WORKFLOW_PARALLEL_DEPTH_LIMIT setting and any related configurations that could affect logging. Ensure that your logging configuration in the Docker setup is correctly set up, as incomplete logging can sometimes be related to configuration issues [1].

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 (May 2, 2025): <!-- Answer --> There is a known issue in Dify version 1.0.1 where not all parallel node executions are fully displayed in the workflow logs when using Iteration or Parallel nodes. This issue has been fixed in a later version through pull request #14855. Since you are using version 1.3.1, this specific issue should not be present. However, if you are experiencing similar log loss, it might be worth checking your logging configurations and settings related to parallelism. Additionally, you might want to review the `WORKFLOW_PARALLEL_DEPTH_LIMIT` setting and any related configurations that could affect logging. Ensure that your logging configuration in the Docker setup is correctly set up, as incomplete logging can sometimes be related to configuration issues <sup>[[1]](https://github.com/langgenius/dify/issues/16773)</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/81c366ea-b54d-4999-ba24-bf270385d1b7?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/81c366ea-b54d-4999-ba24-bf270385d1b7?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/81c366ea-b54d-4999-ba24-bf270385d1b7?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/81c366ea-b54d-4999-ba24-bf270385d1b7?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/81c366ea-b54d-4999-ba24-bf270385d1b7?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/81c366ea-b54d-4999-ba24-bf270385d1b7?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/81c366ea-b54d-4999-ba24-bf270385d1b7?feedback_type=other)</sup>
yindo commented 2026-02-21 19:12:57 -05:00
Author
Owner
Copy Link
Copy Source

@fdb02983rhy commented on GitHub (May 2, 2025):

Same problem here

@fdb02983rhy commented on GitHub (May 2, 2025): Same problem here
yindo commented 2026-02-21 19:12:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Aug 24, 2025):

Hi, @auxpd. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported missing log entries from loop nodes in parallel workflows on Dify v1.3.1 (self-hosted via Docker).
  • A similar issue was fixed after v1.0.1, so it was expected not to affect v1.3.1.
  • Suggestions were made to verify logging configurations and the WORKFLOW_PARALLEL_DEPTH_LIMIT setting.
  • Another user confirmed experiencing the same problem, indicating it might still occur under certain conditions.
  • The issue remains unresolved with no recent updates.

Next Steps:

  • Please confirm if this issue is still relevant with the latest version of Dify by commenting here.
  • If no further activity occurs, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Aug 24, 2025): Hi, @auxpd. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported missing log entries from loop nodes in parallel workflows on Dify v1.3.1 (self-hosted via Docker). - A similar issue was fixed after v1.0.1, so it was expected not to affect v1.3.1. - Suggestions were made to verify logging configurations and the WORKFLOW_PARALLEL_DEPTH_LIMIT setting. - Another user confirmed experiencing the same problem, indicating it might still occur under certain conditions. - The issue remains unresolved with no recent updates. **Next Steps:** - Please confirm if this issue is still relevant with the latest version of Dify by commenting here. - If no further activity occurs, I will automatically close this issue in 15 days. Thank you for your understanding and contribution!
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
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#13602
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?