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

Knowledge pipeline cannot be created in 1.10.0 [Knowledge Base] This node has not yet been connected to other nodes #20380

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

Originally created by @kkxlys on GitHub (Nov 18, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

<img width="576" height="126" alt="Image

Image

" src="https://github.com/user-attachments/assets/65301bd3-d14a-4a5e-b75b-81dc22c209df" />

✔️ Expected Behavior

I hope it can be released normally

❌ Actual Behavior

No response

Originally created by @kkxlys on GitHub (Nov 18, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="576" height="126" alt="Image <img width="3840" height="2088" alt="Image" src="https://github.com/user-attachments/assets/33087492-31a2-4889-870e-c675e64af590" /> " src="https://github.com/user-attachments/assets/65301bd3-d14a-4a5e-b75b-81dc22c209df" /> ### ✔️ Expected Behavior I hope it can be released normally ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 20:07:07 -05:00
yindo closed this issue 2026-02-21 20:07:07 -05:00
yindo commented 2026-02-21 20:07:07 -05:00
Author
Owner
Copy Link
Copy Source

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

The error "This node has not yet been connected to other nodes" usually means the Knowledge Base node isn't properly connected in the pipeline graph. In Dify, only nodes that are reachable from a "Start" or trigger node are considered valid parts of the workflow. If the Knowledge Base node isn't connected by edges all the way back to a Start/trigger node, or if required input variables (like "Chunks") aren't mapped from upstream nodes, you'll see this error and won't be able to release the pipeline. Double-check that every node is connected in sequence and that the Knowledge Base node's input matches the expected chunk structure and variable name "Chunks".

Also, if you're using plugins like MinerU, make sure their output schemas are detailed enough for the variable picker to recognize and propagate fields downstream—otherwise, required variables might not show up as connectable options, causing this error as well "MinerU plugin schema issue".

If you're running Dify via Docker, ensure all required services (like the vector database) are running, environment variables are set correctly, and the API service port (usually 5001) is exposed and mapped in your docker-compose.yaml file. Missing or misconfigured services can also cause pipeline nodes to appear unconnected or fail to initialize "Docker config troubleshooting".

If you check these areas and still have trouble, try simplifying the pipeline to a minimal working example and add nodes back one at a time to isolate where the connection breaks.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 18, 2025): <!-- Answer --> The error "This node has not yet been connected to other nodes" usually means the Knowledge Base node isn't properly connected in the pipeline graph. In Dify, only nodes that are reachable from a "Start" or trigger node are considered valid parts of the workflow. If the Knowledge Base node isn't connected by edges all the way back to a Start/trigger node, or if required input variables (like "Chunks") aren't mapped from upstream nodes, you'll see this error and won't be able to release the pipeline. Double-check that every node is connected in sequence and that the Knowledge Base node's input matches the expected chunk structure and variable name ["Chunks"](https://github.com/langgenius/dify/blob/c4b02be6d35e859d3789222ef6ee2d860ae474a3/web/i18n/en-US/workflow.ts#L50-L1066). Also, if you're using plugins like MinerU, make sure their output schemas are detailed enough for the variable picker to recognize and propagate fields downstream—otherwise, required variables might not show up as connectable options, causing this error as well ["MinerU plugin schema issue"](https://github.com/langgenius/dify-official-plugins/issues/2074). If you're running Dify via Docker, ensure all required services (like the vector database) are running, environment variables are set correctly, and the API service port (usually 5001) is exposed and mapped in your `docker-compose.yaml` file. Missing or misconfigured services can also cause pipeline nodes to appear unconnected or fail to initialize ["Docker config troubleshooting"](https://github.com/langgenius/dify-official-plugins/issues/1816). If you check these areas and still have trouble, try simplifying the pipeline to a minimal working example and add nodes back one at a time to isolate where the connection breaks. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/67bf922d-beb6-43b1-9e91-da4e07d986cf?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/67bf922d-beb6-43b1-9e91-da4e07d986cf?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/67bf922d-beb6-43b1-9e91-da4e07d986cf?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/67bf922d-beb6-43b1-9e91-da4e07d986cf?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/67bf922d-beb6-43b1-9e91-da4e07d986cf?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/67bf922d-beb6-43b1-9e91-da4e07d986cf?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/67bf922d-beb6-43b1-9e91-da4e07d986cf?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28322)
yindo commented 2026-02-21 20:07:07 -05:00
Author
Owner
Copy Link
Copy Source

@JohnJyong commented on GitHub (Nov 18, 2025):

#28203 @kkxlys the issue has fixed， it will be inclouded in the next release.

@JohnJyong commented on GitHub (Nov 18, 2025): #28203 @kkxlys the issue has fixed， it will be inclouded in the next release.
yindo commented 2026-02-21 20:07:07 -05:00
Author
Owner
Copy Link
Copy Source

@kkxlys commented on GitHub (Nov 18, 2025):

#28203 @kkxlys问题已修复，将在下一个版本中修复。

ok，thank you，but i have a question，When is the next version expected to be released

@kkxlys commented on GitHub (Nov 18, 2025): > [#28203](https://github.com/langgenius/dify/pull/28203) [@kkxlys](https://github.com/kkxlys)问题已修复，将在下一个版本中修复。 ok，thank you，but i have a question，When is the next version expected to be released
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#20380
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?