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 BUG #20391

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

Originally created by @Chivenh 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

v1.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image

✔️ Expected Behavior

I had made a RAG dataset. But I can't publish it.

❌ Actual Behavior

It show me an error with '[File] This node has not yet been connected to other nodes'

Originally created by @Chivenh 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 v1.10.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="659" height="300" alt="Image" src="https://github.com/user-attachments/assets/9e768fea-49bf-4899-976a-f770ed0c7d62" /> ### ✔️ Expected Behavior I had made a RAG dataset. But I can't publish it. ### ❌ Actual Behavior It show me an error with '[File] This node has not yet been connected to other nodes'
yindo added the 🐞 bugKnowledge Pipeline labels 2026-02-21 20:07:11 -05:00
yindo closed this issue 2026-02-21 20:07:11 -05:00
yindo commented 2026-02-21 20:07:12 -05:00
Author
Owner
Copy Link
Copy Source

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

This is a known bug in Dify v1.10.0 (and v1.10.1) where the workflow publishing validation is too strict and incorrectly flags terminal nodes (like FILE or KNOWLEDGE BASE) as "not connected to anything," even if your pipeline is logically complete and test runs succeed. There is no configuration workaround for this in v1.10.0; the only reliable solution is to upgrade to a newer Dify release where this bug is fixed. The fix was merged in PR #28203 and will be included in any version released after 2025-11-14, which restores the ability to publish workflows with terminal nodes as expected. See details and confirmation in this issue and PR #28203.

If you can't upgrade right away, double-check that your pipeline has a designated start node and all nodes are properly connected, but be aware that the publishing block is due to the validation bug, not your pipeline logic. If you need help with upgrade steps or troubleshooting, let me know!

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 --> This is a known bug in Dify v1.10.0 (and v1.10.1) where the workflow publishing validation is too strict and incorrectly flags terminal nodes (like FILE or KNOWLEDGE BASE) as "not connected to anything," even if your pipeline is logically complete and test runs succeed. There is no configuration workaround for this in v1.10.0; the only reliable solution is to upgrade to a newer Dify release where this bug is fixed. The fix was merged in PR #28203 and will be included in any version released after 2025-11-14, which restores the ability to publish workflows with terminal nodes as expected. See details and confirmation in [this issue](https://github.com/langgenius/dify/issues/28322) and [PR #28203](https://github.com/langgenius/dify/pull/28203). If you can't upgrade right away, double-check that your pipeline has a designated start node and all nodes are properly connected, but be aware that the publishing block is due to the validation bug, not your pipeline logic. If you need help with upgrade steps or troubleshooting, let me know! <!-- 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/5edf3d6f-88df-4016-9dc3-062a33ace1f0?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5edf3d6f-88df-4016-9dc3-062a33ace1f0?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5edf3d6f-88df-4016-9dc3-062a33ace1f0?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5edf3d6f-88df-4016-9dc3-062a33ace1f0?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5edf3d6f-88df-4016-9dc3-062a33ace1f0?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5edf3d6f-88df-4016-9dc3-062a33ace1f0?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5edf3d6f-88df-4016-9dc3-062a33ace1f0?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/28352)
yindo commented 2026-02-21 20:07:12 -05:00
Author
Owner
Copy Link
Copy Source

@rsfdwecsd commented on GitHub (Nov 20, 2025):

I also encountered the same problem, I upgraded to version 1.10.0 this morning. I was prompted when publishing the knowledge pipeline that this step is not connected to anything.

Image
@rsfdwecsd commented on GitHub (Nov 20, 2025): I also encountered the same problem, I upgraded to version 1.10.0 this morning. I was prompted when publishing the knowledge pipeline that this step is not connected to anything. <img width="2172" height="1112" alt="Image" src="https://github.com/user-attachments/assets/5ba1a293-fe91-485b-b62b-76b81744aec9" />
yindo commented 2026-02-21 20:07:12 -05:00
Author
Owner
Copy Link
Copy Source

@davidkhala commented on GitHub (Dec 3, 2025):

@rsfdwecsd @Chivenh I saw the same problem in 1.10.0. Upgrade to 1.10.1 can resolve this problem in my experiment

  • My upgrade only includes change to use images langgenius/dify-web:1.10.1 and langgenius/dify-api:1.10.1, while keep all data including pipeline definition as-is.
  • You might see Permission denied (os error 13) if you are using named volume for langgenius/dify-api:1.10.1 image in Docker Desktop for Win
@davidkhala commented on GitHub (Dec 3, 2025): @rsfdwecsd @Chivenh I saw the same problem in 1.10.0. Upgrade to 1.10.1 can resolve this problem in my experiment - My upgrade only includes change to use images `langgenius/dify-web:1.10.1` and `langgenius/dify-api:1.10.1`, while keep all data including pipeline definition as-is. - You might see `Permission denied (os error 13)` if you are using named volume for `langgenius/dify-api:1.10.1` image in Docker Desktop for Win
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 Knowledge Pipeline 🐞 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#20391
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?