langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 22:11:36 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

[File] This step is not connected to anything #20320

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

Originally created by @shy20221121 on GitHub (Nov 13, 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

An error occurs when publishing a pipeline knowledge base workflow.
Both creating a knowledge base using a template and creating a blank pipeline knowledge base result in an error when clicking "Publish," preventing publication.

See image:
Using a template:

Image

Manual creation:

Image

✔️ Expected Behavior

The pipeline process is expected to be released normally.

❌ Actual Behavior

No response

Originally created by @shy20221121 on GitHub (Nov 13, 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 An error occurs when publishing a pipeline knowledge base workflow. Both creating a knowledge base using a template and creating a blank pipeline knowledge base result in an error when clicking "Publish," preventing publication. See image: Using a template: <img width="930" height="347" alt="Image" src="https://github.com/user-attachments/assets/3b4bbddf-1bde-439f-8cb9-3cc77b5dd010" /> Manual creation: <img width="851" height="381" alt="Image" src="https://github.com/user-attachments/assets/33019719-3e8f-4247-970e-d37fbe8fa10f" /> ### ✔️ Expected Behavior The pipeline process is expected to be released normally. ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug🌊 feat:workflow labels 2026-02-21 20:06:48 -05:00
yindo closed this issue 2026-02-21 20:06:48 -05:00
yindo commented 2026-02-21 20:06:49 -05:00
Author
Owner
Copy Link
Copy Source

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

This error is a known bug in Dify v1.10.1 (self-hosted, Docker): 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 workflow is logically complete and test runs succeed. There is no configuration workaround for this in v1.10.1; the only reliable solution is to upgrade to a newer Dify release where this bug is fixed. You can see the details and confirmation in this issue and the recent fix in PR #28203.

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 13, 2025): <!-- Answer --> This error is a known bug in Dify v1.10.1 (self-hosted, Docker): 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 workflow is logically complete and test runs succeed. There is no configuration workaround for this in v1.10.1; the only reliable solution is to upgrade to a newer Dify release where this bug is fixed. You can see the details and confirmation in [this issue](https://github.com/langgenius/dify/issues/27671) and the recent fix in [PR #28203](https://github.com/langgenius/dify/pull/28203). 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/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?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/28208)
yindo commented 2026-02-21 20:06:49 -05:00
Author
Owner
Copy Link
Copy Source

@shy20221121 commented on GitHub (Nov 13, 2025):

This error is a known bug in Dify v1.10.1 (self-hosted, Docker): 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 workflow is logically complete and test runs succeed. There is no configuration workaround for this in v1.10.1; the only reliable solution is to upgrade to a newer Dify release where this bug is fixed. You can see the details and confirmation in this issue and the recent fix in PR #28203.

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

@dosu Is there a temporary solution?

@shy20221121 commented on GitHub (Nov 13, 2025): > This error is a known bug in Dify v1.10.1 (self-hosted, Docker): 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 workflow is logically complete and test runs succeed. There is no configuration workaround for this in v1.10.1; the only reliable solution is to upgrade to a newer Dify release where this bug is fixed. You can see the details and confirmation in [this issue](https://github.com/langgenius/dify/issues/27671) and the recent fix in [PR #28203](https://github.com/langgenius/dify/pull/28203). > > If you need help with upgrade steps or troubleshooting, let me know! > > _To reply, just mention [@dosu](https://go.dosu.dev/dosubot)._ > > How did I do? [Good](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/f339ab0e-1032-4f43-b048-e140e89e713d?feedback_type=other)  [![Chat with Dosu](https://camo.githubusercontent.com/7c571478962a6b8a5d47cac74b6824c75e4f6731bba52377e6007f9150462923/68747470733a2f2f646f73752e6465762f646f73752d636861742d62616467652e737667)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Join Discord](https://camo.githubusercontent.com/7d2066700925db1e370d956834f9ea0e5bc92cecbe84963fbd2a363e45091b4e/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6a6f696e2d3538363546323f6c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465266c6162656c3d)](https://go.dosu.dev/discord-bot) [![Share on X](https://camo.githubusercontent.com/a8bd7f3fcf3f5e3bd124eee9ae50ae2ac17b40971726665ac2121d48f9aee155/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f582d73686172652d626c61636b)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28208) @dosu Is there a temporary solution?
yindo commented 2026-02-21 20:06:49 -05:00
Author
Owner
Copy Link
Copy Source

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

There isn't a temporary workaround for this bug in Dify v1.10.1—upgrading to a newer version is the only reliable fix. The validation logic in these versions doesn't recognize terminal nodes (like FILE or KNOWLEDGE BASE) as valid endpoints, so publishing is blocked even if your workflow is correct and test runs succeed. This was fixed in later releases, and no configuration or manual hack is documented or recommended for bypassing the check. If you need help with upgrade steps, 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 13, 2025): <!-- Answer --> There isn't a temporary workaround for this bug in Dify v1.10.1—upgrading to a newer version is the only reliable fix. The validation logic in these versions doesn't recognize terminal nodes (like FILE or KNOWLEDGE BASE) as valid endpoints, so publishing is blocked even if your workflow is correct and test runs succeed. This was fixed in later releases, and no configuration or manual hack is documented or recommended for bypassing the check. If you need help with upgrade steps, 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/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?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/28208)
yindo commented 2026-02-21 20:06:49 -05:00
Author
Owner
Copy Link
Copy Source

@shy20221121 commented on GitHub (Nov 13, 2025):

There isn't a temporary workaround for this bug in Dify v1.10.1—upgrading to a newer version is the only reliable fix. The validation logic in these versions doesn't recognize terminal nodes (like FILE or KNOWLEDGE BASE) as valid endpoints, so publishing is blocked even if your workflow is correct and test runs succeed. This was fixed in later releases, and no configuration or manual hack is documented or recommended for bypassing the check. If you need help with upgrade steps, 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

@dosu Dify v1.10.1 is already the latest version, right? What version can I upgrade to?

@shy20221121 commented on GitHub (Nov 13, 2025): > There isn't a temporary workaround for this bug in Dify v1.10.1—upgrading to a newer version is the only reliable fix. The validation logic in these versions doesn't recognize terminal nodes (like FILE or KNOWLEDGE BASE) as valid endpoints, so publishing is blocked even if your workflow is correct and test runs succeed. This was fixed in later releases, and no configuration or manual hack is documented or recommended for bypassing the check. If you need help with upgrade steps, let me know! > > _To reply, just mention [@dosu](https://go.dosu.dev/dosubot)._ > > How did I do? [Good](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/e1fdcbed-4579-485d-b40a-592f9e9e1bdf?feedback_type=other)  [![Chat with Dosu](https://camo.githubusercontent.com/7c571478962a6b8a5d47cac74b6824c75e4f6731bba52377e6007f9150462923/68747470733a2f2f646f73752e6465762f646f73752d636861742d62616467652e737667)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Join Discord](https://camo.githubusercontent.com/7d2066700925db1e370d956834f9ea0e5bc92cecbe84963fbd2a363e45091b4e/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6a6f696e2d3538363546323f6c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465266c6162656c3d)](https://go.dosu.dev/discord-bot) [![Share on X](https://camo.githubusercontent.com/a8bd7f3fcf3f5e3bd124eee9ae50ae2ac17b40971726665ac2121d48f9aee155/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f582d73686172652d626c61636b)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28208) @dosu Dify v1.10.1 is already the latest version, right? What version can I upgrade to?
yindo commented 2026-02-21 20:06:49 -05:00
Author
Owner
Copy Link
Copy Source

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

Dify v1.10.1 is not the latest version—there is a newer release that includes the fix for the workflow publishing validation bug. The fix was merged on 2025-11-14 (PR #28203), so any version released after that date will resolve the issue with terminal nodes like FILE or KNOWLEDGE BASE being incorrectly flagged as "not connected to anything." Upgrading to the latest available version after v1.10.1 will allow you to publish your pipeline workflows as expected.

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 13, 2025): <!-- Answer --> Dify v1.10.1 is not the latest version—there is a newer release that includes the fix for the workflow publishing validation bug. The fix was merged on 2025-11-14 ([PR #28203](https://github.com/langgenius/dify/pull/28203)), so any version released after that date will resolve the issue with terminal nodes like FILE or KNOWLEDGE BASE being incorrectly flagged as "not connected to anything." Upgrading to the latest available version after v1.10.1 will allow you to publish your pipeline workflows as expected. <!-- 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/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?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/28208)
yindo commented 2026-02-21 20:06:49 -05:00
Author
Owner
Copy Link
Copy Source

@shy20221121 commented on GitHub (Nov 13, 2025):

Dify v1.10.1 is not the latest version—there is a newer release that includes the fix for the workflow publishing validation bug. The fix was merged on 2025-11-14 (PR #28203), so any version released after that date will resolve the issue with terminal nodes like FILE or KNOWLEDGE BASE being incorrectly flagged as "not connected to anything." Upgrading to the latest available version after v1.10.1 will allow you to publish your pipeline workflows as expected.

To reply, just mention @dosu.

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

ok, thanks

@shy20221121 commented on GitHub (Nov 13, 2025): > Dify v1.10.1 is not the latest version—there is a newer release that includes the fix for the workflow publishing validation bug. The fix was merged on 2025-11-14 ([PR #28203](https://github.com/langgenius/dify/pull/28203)), so any version released after that date will resolve the issue with terminal nodes like FILE or KNOWLEDGE BASE being incorrectly flagged as "not connected to anything." Upgrading to the latest available version after v1.10.1 will allow you to publish your pipeline workflows as expected. > > _To reply, just mention [@dosu](https://go.dosu.dev/dosubot)._ > > How did I do? [Good](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/7a69065b-726a-4c92-9269-3268137ae6df?feedback_type=other)  [![Chat with Dosu](https://camo.githubusercontent.com/7c571478962a6b8a5d47cac74b6824c75e4f6731bba52377e6007f9150462923/68747470733a2f2f646f73752e6465762f646f73752d636861742d62616467652e737667)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github) [![Join Discord](https://camo.githubusercontent.com/7d2066700925db1e370d956834f9ea0e5bc92cecbe84963fbd2a363e45091b4e/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f6a6f696e2d3538363546323f6c6f676f3d646973636f7264266c6f676f436f6c6f723d7768697465266c6162656c3d)](https://go.dosu.dev/discord-bot) [![Share on X](https://camo.githubusercontent.com/a8bd7f3fcf3f5e3bd124eee9ae50ae2ac17b40971726665ac2121d48f9aee155/68747470733a2f2f696d672e736869656c64732e696f2f62616467652f582d73686172652d626c61636b)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28208) ok, thanks
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 🐞 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#20320
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?