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

Cannot connect with a node which runs in parallel. #13991

New Issue
Closed
opened 2026-02-21 19:14:57 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 19:14:57 -05:00
Owner
Copy Link
Copy Source

Originally created by @init-ikuya on GitHub (May 18, 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.4.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Create a chat flow.
  2. Create two branches which run in parallel.
  3. Create another node and try to connect it with one of nodes which run in parallel (created in step 2)

✔️ Expected Behavior

We can successfully connect with a node which runs in parallel.

❌ Actual Behavior

We can't connect with a node which runs in parallel.

https://github.com/user-attachments/assets/7739b291-2292-4a9e-a3cf-c71276155442

Originally created by @init-ikuya on GitHub (May 18, 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.4.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Create a chat flow. 2. Create two branches which run in parallel. 3. Create another node and try to connect it with one of nodes which run in parallel (created in step 2) ### ✔️ Expected Behavior We can successfully connect with a node which runs in parallel. ### ❌ Actual Behavior We can't connect with a node which runs in parallel. https://github.com/user-attachments/assets/7739b291-2292-4a9e-a3cf-c71276155442
yindo added the 🌊 feat:workflow label 2026-02-21 19:14:57 -05:00
yindo closed this issue 2026-02-21 19:14:58 -05:00
yindo commented 2026-02-21 19:14:58 -05:00
Author
Owner
Copy Link
Copy Source

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

Hello @init-ikuya! I'm Dosu, your friendly bot here to help you with bugs, questions, and becoming a contributor. I'm ready to assist you while we wait for a human maintainer. How can I help you today?

In Dify version 1.4.0, there is a known limitation where nodes cannot have multiple incoming connections from different branching nodes due to a technical constraint in Dify's Graph design. Each node can only have a single incoming connection path, which means you cannot connect a node to multiple parallel branches [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 18, 2025): <!-- Greeting --> Hello @init-ikuya! I'm [Dosu](https://dosu.dev), your friendly bot here to help you with bugs, questions, and becoming a contributor. I'm ready to assist you while we wait for a human maintainer. How can I help you today? <!-- Answer --> In Dify version 1.4.0, there is a known limitation where nodes cannot have multiple incoming connections from different branching nodes due to a technical constraint in Dify's Graph design. Each node can only have a single incoming connection path, which means you cannot connect a node to multiple parallel branches <sup>[[1]](https://github.com/langgenius/dify/issues/18233)</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/4f2657cf-99cd-409c-89f2-4d67d148ce77?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/4f2657cf-99cd-409c-89f2-4d67d148ce77?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/4f2657cf-99cd-409c-89f2-4d67d148ce77?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/4f2657cf-99cd-409c-89f2-4d67d148ce77?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/4f2657cf-99cd-409c-89f2-4d67d148ce77?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/4f2657cf-99cd-409c-89f2-4d67d148ce77?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/4f2657cf-99cd-409c-89f2-4d67d148ce77?feedback_type=other)</sup>
yindo commented 2026-02-21 19:14:58 -05:00
Author
Owner
Copy Link
Copy Source

@init-ikuya commented on GitHub (May 19, 2025):

@dosu Does this community have a plan to Change the limitation ?

@init-ikuya commented on GitHub (May 19, 2025): @dosu Does this community have a plan to Change the limitation ?
yindo commented 2026-02-21 19:14:58 -05:00
Author
Owner
Copy Link
Copy Source

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

I wasn't able to find any specific information about ongoing discussions or proposals in the Dify community regarding changes to the Graph design to address this limitation. It might be worth checking the repository's issues or discussions for any updates or proposals that might not have been captured here.

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 19, 2025): <!-- Answer --> I wasn't able to find any specific information about ongoing discussions or proposals in the Dify community regarding changes to the Graph design to address this limitation. It might be worth checking the repository's issues or discussions for any updates or proposals that might not have been captured here. <!-- 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/0897e552-6a0c-48d2-bacc-5ade3741454c?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/0897e552-6a0c-48d2-bacc-5ade3741454c?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/0897e552-6a0c-48d2-bacc-5ade3741454c?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/0897e552-6a0c-48d2-bacc-5ade3741454c?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/0897e552-6a0c-48d2-bacc-5ade3741454c?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/0897e552-6a0c-48d2-bacc-5ade3741454c?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/0897e552-6a0c-48d2-bacc-5ade3741454c?feedback_type=other)</sup>
yindo commented 2026-02-21 19:14:58 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Aug 29, 2025):

They are in the different branches, so I don't understand how they can be run together.

@crazywoola commented on GitHub (Aug 29, 2025): They are in the different branches, so I don't understand how they can be run together.
yindo commented 2026-02-21 19:14:58 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Sep 29, 2025):

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

Issue Summary:

  • You reported that in Dify v1.4.0 (self-hosted), connecting a node to parallel nodes within a chat flow is not possible, although creating parallel branches works fine.
  • This limitation is due to Dify's graph design, which currently allows only one incoming connection per node.
  • You asked if there are plans to change this limitation, but no updates or proposals have been shared so far.
  • Another user raised questions about the feasibility of running nodes in different branches together, but no resolution has been reached.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Sep 29, 2025): Hi, @init-ikuya. 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 that in Dify v1.4.0 (self-hosted), connecting a node to parallel nodes within a chat flow is not possible, although creating parallel branches works fine. - This limitation is due to Dify's graph design, which currently allows only one incoming connection per node. - You asked if there are plans to change this limitation, but no updates or proposals have been shared so far. - Another user raised questions about the feasibility of running nodes in different branches together, but no resolution has been reached. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - Otherwise, 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 🌊 feat:workflow
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#13991
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?