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

Knowledge pipeline cannot be created in 1.10.0-rc1 without start node #20202

New Issue
Closed
opened 2026-02-21 20:06:17 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:06:17 -05:00
Owner
Copy Link
Copy Source

Originally created by @chunglam2525 on GitHub (Nov 7, 2025).

Originally assigned to: @hjlarry on GitHub.

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-rc1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Create any pre-existing knowledge pipeline template

✔️ Expected Behavior

Pipeline template should be able to publish out of the box

❌ Actual Behavior

Error: At least one start node must be added

Possibly due to changes with added Trigger node logic without handling pipeline case.
Since I believe this two features were developed in parallel branch.

Originally created by @chunglam2525 on GitHub (Nov 7, 2025). Originally assigned to: @hjlarry on GitHub. ### 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-rc1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Create any pre-existing knowledge pipeline template ### ✔️ Expected Behavior Pipeline template should be able to publish out of the box ### ❌ Actual Behavior Error: At least one start node must be added Possibly due to changes with added Trigger node logic without handling pipeline case. Since I believe this two features were developed in parallel branch.
yindo added the 🐞 bug label 2026-02-21 20:06:17 -05:00
yindo closed this issue 2026-02-21 20:06:17 -05:00
yindo commented 2026-02-21 20:06:17 -05:00
Author
Owner
Copy Link
Copy Source

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

This is a known bug in Dify v1.10.0-rc1: publishing a knowledge pipeline template fails with “At least one start node must be added” even if your pipeline is logically complete and test runs succeed. The issue is caused by stricter validation introduced with recent trigger node logic changes—pipelines without a classic start node (like those using only triggers or data sources) are incorrectly blocked from publishing. This regression happened because trigger and pipeline features were developed in parallel and not fully integrated in this release. There’s no configuration workaround in v1.10.0-rc1; upgrading to a newer version where this bug is fixed is the recommended solution (details and confirmation). If you’re blocked from publishing, you’ll need to upgrade or patch the validation logic in your deployment.

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 7, 2025): <!-- Answer --> This is a known bug in Dify v1.10.0-rc1: publishing a knowledge pipeline template fails with “At least one start node must be added” even if your pipeline is logically complete and test runs succeed. The issue is caused by stricter validation introduced with recent trigger node logic changes—pipelines without a classic start node (like those using only triggers or data sources) are incorrectly blocked from publishing. This regression happened because trigger and pipeline features were developed in parallel and not fully integrated in this release. There’s no configuration workaround in v1.10.0-rc1; upgrading to a newer version where this bug is fixed is the recommended solution ([details and confirmation](https://github.com/langgenius/dify/issues/27671)). If you’re blocked from publishing, you’ll need to upgrade or patch the validation logic in your deployment. <!-- 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/8f8098a1-ba15-4810-b333-d4447537f93e?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/8f8098a1-ba15-4810-b333-d4447537f93e?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/8f8098a1-ba15-4810-b333-d4447537f93e?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/8f8098a1-ba15-4810-b333-d4447537f93e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8f8098a1-ba15-4810-b333-d4447537f93e?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/8f8098a1-ba15-4810-b333-d4447537f93e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8f8098a1-ba15-4810-b333-d4447537f93e?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/27989)
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#20202
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?