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

How to convert a url string to a File in workflow. #20231

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

Originally created by @kubylo0917-pixel on GitHub (Nov 10, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I just want to use a url string as a input param in workflow, but it can not convert to a remote url File, so I can not use it as a LLM vision input.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @kubylo0917-pixel on GitHub (Nov 10, 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] 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] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. I just want to use a url string as a input param in workflow, but it can not convert to a remote url File, so I can not use it as a LLM vision input. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 🙋‍♂️ question label 2026-02-21 20:06:23 -05:00
yindo closed this issue 2026-02-21 20:06:23 -05:00
yindo commented 2026-02-21 20:06:24 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @kubylo0917-pixel! I'm Dosu and I’m helping the dify team.

You can convert a URL string to a File object in a Dify workflow by using the backend's built-in file handling utilities. Dify provides a method called save_remote_url in the FileSaverImpl class, which downloads the file from the given URL and creates a File object that can be used as input for LLM vision tasks. This method fetches the file content, determines its MIME type and extension, and saves it to storage, making it available to downstream workflow nodes. Here’s the relevant code:

def save_remote_url(self, url: str, file_type: FileType) -> File:
    http_response = ssrf_proxy.get(url)
    http_response.raise_for_status()
    data = http_response.content
    mime_type_from_header = http_response.headers.get("Content-Type")
    mime_type, extension = _extract_content_type_and_extension(url, mime_type_from_header)
    return self.save_binary_string(data, mime_type, file_type, extension_override=extension)

source

If you want to use a URL as a file input in your workflow, you can either call this method directly in a custom node or ensure your workflow input node is configured to accept remote URLs. Dify will then handle the download and conversion automatically, making the file available for LLM vision input or other file-based processing steps. The File model supports this pattern and validates remote URLs as file sources source.

For plugins that require the actual file content (like dify_extractor), make sure the file bytes are loaded and included in the workflow input, as these plugins do not fetch files from URLs themselves. For vision models that accept image URLs, you can pass the URL directly in the expected input format.

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 10, 2025): <!-- Greeting --> Hi @kubylo0917-pixel! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> You can convert a URL string to a File object in a Dify workflow by using the backend's built-in file handling utilities. Dify provides a method called `save_remote_url` in the `FileSaverImpl` class, which downloads the file from the given URL and creates a File object that can be used as input for LLM vision tasks. This method fetches the file content, determines its MIME type and extension, and saves it to storage, making it available to downstream workflow nodes. Here’s the relevant code: ```python def save_remote_url(self, url: str, file_type: FileType) -> File: http_response = ssrf_proxy.get(url) http_response.raise_for_status() data = http_response.content mime_type_from_header = http_response.headers.get("Content-Type") mime_type, extension = _extract_content_type_and_extension(url, mime_type_from_header) return self.save_binary_string(data, mime_type, file_type, extension_override=extension) ``` [source](https://github.com/langgenius/dify/blob/9843fec3931ba791b09a3805e44fbe6636191996/api/core/workflow/nodes/llm/file_saver.py#L65-L123) If you want to use a URL as a file input in your workflow, you can either call this method directly in a custom node or ensure your workflow input node is configured to accept remote URLs. Dify will then handle the download and conversion automatically, making the file available for LLM vision input or other file-based processing steps. The File model supports this pattern and validates remote URLs as file sources [source](https://github.com/langgenius/dify/blob/9843fec3931ba791b09a3805e44fbe6636191996/api/core/file/models.py#L36-L165). For plugins that require the actual file content (like dify_extractor), make sure the file bytes are loaded and included in the workflow input, as these plugins do not fetch files from URLs themselves. For vision models that accept image URLs, you can pass the URL directly in the expected input format. <!-- 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/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?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/28041)
yindo commented 2026-02-21 20:06:24 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi, I’ve run into the same issue.
I used the HTTP request node to convert a URL into a file output, and it works for PDF files.
However, it does not work for Word documents — the response body becomes garbled, and the files[] list is empty.

How should this be handled?

{
"status_code": 200,
"body": "PK\u0003\u0004\u0014\u0000\u0006\u0000\b\u0000\u0000\u0000!\u0000��\n��\u0001\u0000\u0000\u000b\u0006\u0000\u0000\u0013\u0000\b\u0002[Content_Types].xml �\u0004\u0002(�\u0000\u0002\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000��OO�@\u0010��&~�f��]�`��xP<��\u0018��v\n\u001b���3�|{�\u0014\u001b5@A�Ҥ����y�����V�\u001c"\u001a�r��z"\u0001�}a�$\u0017���R$H�\u0015��\u000er�\u0004\u0014��ӓ�x\u0019\u0000\u0013�v��)Q��\u0012�\u0014���\u0007p|R�h\u0015�m�Ƞ����<��.����QJ��\u0018\u000en�T����;?......",
"headers": {
"accept-ranges": "bytes",
"content-length": "17408",
"content-type": "application/vnd.openxmlformats-officedocument.wordprocessingml.document",
"etag": ""f93699a129e0fda5646fef16fd1f9603"",
"last-modified": "Thu, 20 Nov 2025 00:51:28 GMT",
"server": "MinIO",
"strict-transport-security": "max-age=31536000; includeSubDomains",
"vary": "Origin, Accept-Encoding",
"x-amz-id-2": "d0af7ef13e9a79de08686e85c361d9af88c5ebdbbacf07a734ab2c11fd85e57f",
"x-amz-request-id": "187990D6E9A5FCC0",
"x-content-type-options": "nosniff",
"x-xss-protection": "1; mode=block",
"date": "Thu, 20 Nov 2025 00:53:01 GMT",
"cache-status": "5b2242908e68;detail=mismatch",
"via": "1.1 5b2242908e68 (squid/6.10)",
"connection": "keep-alive"
},
"files": []
}

Hi @kubylo0917-pixel! I'm Dosu and I’m helping the dify team.

You can convert a URL string to a File object in a Dify workflow by using the backend's built-in file handling utilities. Dify provides a method called save_remote_url in the FileSaverImpl class, which downloads the file from the given URL and creates a File object that can be used as input for LLM vision tasks. This method fetches the file content, determines its MIME type and extension, and saves it to storage, making it available to downstream workflow nodes. Here’s the relevant code:

def save_remote_url(self, url: str, file_type: FileType) -> File:
http_response = ssrf_proxy.get(url)
http_response.raise_for_status()
data = http_response.content
mime_type_from_header = http_response.headers.get("Content-Type")
mime_type, extension = _extract_content_type_and_extension(url, mime_type_from_header)
return self.save_binary_string(data, mime_type, file_type, extension_override=extension)
source

If you want to use a URL as a file input in your workflow, you can either call this method directly in a custom node or ensure your workflow input node is configured to accept remote URLs. Dify will then handle the download and conversion automatically, making the file available for LLM vision input or other file-based processing steps. The File model supports this pattern and validates remote URLs as file sources source.

For plugins that require the actual file content (like dify_extractor), make sure the file bytes are loaded and included in the workflow input, as these plugins do not fetch files from URLs themselves. For vision models that accept image URLs, you can pass the URL directly in the expected input format.

To reply, just mention @dosu.

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

@FengfengLiang1112222 commented on GitHub (Nov 20, 2025): Hi, I’ve run into the same issue. I used the HTTP request node to convert a URL into a file output, and it works for PDF files. However, it does not work for Word documents — the response body becomes garbled, and the files[] list is empty. How should this be handled? { "status_code": 200, "body": "PK\u0003\u0004\u0014\u0000\u0006\u0000\b\u0000\u0000\u0000!\u0000��\n��\u0001\u0000\u0000\u000b\u0006\u0000\u0000\u0013\u0000\b\u0002[Content_Types].xml �\u0004\u0002(�\u0000\u0002\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000��OO�@\u0010��&~�f��]�`��xP<��\u0018��v\n\u001b���3�|{�\u0014\u001b5@A�Ҥ����y�����V�\u001c"\u001a�r��z"\u0001�}a�$\u0017���R$H�\u0015��\u000er�\u0004\u0014��ӓ�x\u0019\u0000\u0013�v��)Q��\u0012�\u0014���\u0007p|R�h\u0015�m�Ƞ����<��.����QJ��\u0018\u000en�T����;?......", "headers": { "accept-ranges": "bytes", "content-length": "17408", "content-type": "application/vnd.openxmlformats-officedocument.wordprocessingml.document", "etag": ""f93699a129e0fda5646fef16fd1f9603"", "last-modified": "Thu, 20 Nov 2025 00:51:28 GMT", "server": "MinIO", "strict-transport-security": "max-age=31536000; includeSubDomains", "vary": "Origin, Accept-Encoding", "x-amz-id-2": "d0af7ef13e9a79de08686e85c361d9af88c5ebdbbacf07a734ab2c11fd85e57f", "x-amz-request-id": "187990D6E9A5FCC0", "x-content-type-options": "nosniff", "x-xss-protection": "1; mode=block", "date": "Thu, 20 Nov 2025 00:53:01 GMT", "cache-status": "5b2242908e68;detail=mismatch", "via": "1.1 5b2242908e68 (squid/6.10)", "connection": "keep-alive" }, "files": [] } > Hi [@kubylo0917-pixel](https://github.com/kubylo0917-pixel)! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. > > You can convert a URL string to a File object in a Dify workflow by using the backend's built-in file handling utilities. Dify provides a method called `save_remote_url` in the `FileSaverImpl` class, which downloads the file from the given URL and creates a File object that can be used as input for LLM vision tasks. This method fetches the file content, determines its MIME type and extension, and saves it to storage, making it available to downstream workflow nodes. Here’s the relevant code: > > def save_remote_url(self, url: str, file_type: FileType) -> File: > http_response = ssrf_proxy.get(url) > http_response.raise_for_status() > data = http_response.content > mime_type_from_header = http_response.headers.get("Content-Type") > mime_type, extension = _extract_content_type_and_extension(url, mime_type_from_header) > return self.save_binary_string(data, mime_type, file_type, extension_override=extension) > [source](https://github.com/langgenius/dify/blob/9843fec3931ba791b09a3805e44fbe6636191996/api/core/workflow/nodes/llm/file_saver.py#L65-L123) > > If you want to use a URL as a file input in your workflow, you can either call this method directly in a custom node or ensure your workflow input node is configured to accept remote URLs. Dify will then handle the download and conversion automatically, making the file available for LLM vision input or other file-based processing steps. The File model supports this pattern and validates remote URLs as file sources [source](https://github.com/langgenius/dify/blob/9843fec3931ba791b09a3805e44fbe6636191996/api/core/file/models.py#L36-L165). > > For plugins that require the actual file content (like dify_extractor), make sure the file bytes are loaded and included in the workflow input, as these plugins do not fetch files from URLs themselves. For vision models that accept image URLs, you can pass the URL directly in the expected input format. > > _To reply, just mention [@dosu](https://go.dosu.dev/dosubot)._ > > How did I do? [Good](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/6d467257-18bd-4d18-a44e-4a929f53000e?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/28041)
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 🙋‍♂️ question
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#20231
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?