The knowledge assembly line prompt node is not connected to any other nodes.

[sondervyn]

Self Checks

• 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.

Content

When the knowledge assembly line was released, it prompted that the nodes were not connected to other nodes. In fact, they were already connected and the test run had passed, but it still could not be released.

[dosubot[bot]]

Hi @dingenfeng! I'm Dosu and I’m helping the dify team.

This issue is caused by how Dify’s frontend validates node connectivity before allowing a workflow to be published. Even if your nodes are visually connected and test runs pass, the release can be blocked if the validation logic determines a node is not part of the connected graph starting from a valid start or trigger node. This check is enforced in the checklist and pre-publish guard, which uses a traversal algorithm to find all reachable nodes; any node not included is flagged as “not connected” and blocks publishing—even if it works in test runs. Recent updates improved this logic to better handle start nodes and app modes, but the core rule remains: every node (except valid start/trigger nodes) must be reachable from a start node to pass the release check. If you’re still seeing this prompt, double-check that your workflow’s logical connections match what the frontend expects, and that you’re on a version including the latest fixes for this validation logic (details, code reference).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[sondervyn]

I'm fairly certain my pipeline is working correctly, because even after converting a knowledge base created using traditional methods to pipelined mode, I was unable to publish it, receiving the message: "Knowledge base is not connected to other nodes," even though it is actually connected. Furthermore, my environment is a Docker deployment using version 1.10.0.

[dosubot[bot]]

This is a known issue in Dify 1.10.0: the frontend validation for publishing requires every node (except valid start/trigger nodes) to be reachable from a start node, and the logic can be stricter than what the test run checks. When converting a traditional knowledge base to pipelined mode, if any node isn't recognized as part of the connected graph from a valid start or trigger node, publishing will be blocked—even if the workflow runs fine in tests. Recent versions have improved this validation and fixed false negatives, especially for start nodes and knowledge pipelines. Upgrading to a newer version that includes these fixes (see this PR) should resolve the issue. If you must stay on 1.10.0, double-check that your pipeline has a valid start node and all nodes are connected according to the frontend's expectations, as visual connections alone may not be enough for the publish check to pass.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}