langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Import chatflow to workflow #16601

New Issue
Closed
opened 2026-02-21 19:26:50 -05:00 by yindo · 6 comments
yindo commented 2026-02-21 19:26:50 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Sep 1, 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.7.2

Cloud or Self Hosted

Cloud

Steps to reproduce

Create a chatflow
Export its DSL
Create a workflow
from inside the workflow, use import and choose the chatflow DSL

✔️ Expected Behavior

If any node that cannot be used in workflows is present, the import should fail

❌ Actual Behavior

Image
Originally created by @DavideDelbianco on GitHub (Sep 1, 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.7.2 ### Cloud or Self Hosted Cloud ### Steps to reproduce Create a chatflow Export its DSL Create a workflow from inside the workflow, use import and choose the chatflow DSL ### ✔️ Expected Behavior If any node that cannot be used in workflows is present, the import should fail ### ❌ Actual Behavior <img width="1465" height="264" alt="Image" src="https://github.com/user-attachments/assets/af04a1ec-9a5e-4e02-b7de-c0614d144d6f" />
yindo added the 🐞 bug🌊 feat:workflow labels 2026-02-21 19:26:50 -05:00
yindo closed this issue 2026-02-21 19:26:50 -05:00
yindo commented 2026-02-21 19:26:50 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 2, 2025):

Hi, @DavideDelbianco. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You reported that in Dify version 1.7.2 Cloud, importing a chatflow DSL into a workflow does not fail even when unsupported nodes are included.
  • The expected behavior is for the import process to detect unsupported nodes and fail accordingly.
  • There has been no further activity or comments on this issue since your report.
  • The issue remains unresolved.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here.
  • If I do not hear back within 15 days, I will automatically close this issue.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Oct 2, 2025): Hi, @DavideDelbianco. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You reported that in Dify version 1.7.2 Cloud, importing a chatflow DSL into a workflow does not fail even when unsupported nodes are included. - The expected behavior is for the import process to detect unsupported nodes and fail accordingly. - There has been no further activity or comments on this issue since your report. - The issue remains unresolved. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here. - If I do not hear back within 15 days, I will automatically close this issue. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:26:51 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Oct 8, 2025):

@dosu still possible

@DavideDelbianco commented on GitHub (Oct 8, 2025): @dosu still possible
yindo commented 2026-02-21 19:26:51 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 8, 2025):

@crazywoola The user confirmed the issue with importing chatflow DSL containing unsupported nodes in Dify 1.7.2 Cloud is still present and needs attention. Could you please assist?

@dosubot[bot] commented on GitHub (Oct 8, 2025): @crazywoola The user confirmed the issue with importing chatflow DSL containing unsupported nodes in Dify 1.7.2 Cloud is still present and needs attention. Could you please assist?
yindo commented 2026-02-21 19:26:51 -05:00
Author
Owner
Copy Link
Copy Source

@yangzheli commented on GitHub (Nov 5, 2025):

I can try to fix it. Please assign it to me. @crazywoola

@yangzheli commented on GitHub (Nov 5, 2025): I can try to fix it. Please assign it to me. @crazywoola
yindo commented 2026-02-21 19:26:51 -05:00
Author
Owner
Copy Link
Copy Source

@yangzheli commented on GitHub (Nov 6, 2025):

@dosubot find out the cause and give me a solution

@yangzheli commented on GitHub (Nov 6, 2025): @dosubot find out the cause and give me a solution
yindo commented 2026-02-21 19:26:51 -05:00
Author
Owner
Copy Link
Copy Source

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

The root cause is that the import process does not strictly validate node compatibility between chatflows and workflows. The code recognizes node types and has a list of allowed workflow node types, but the enforcement is incomplete—so incompatible nodes can slip through and be imported.

To fix this, update the import logic (in fromChatflowDsl.ts) to explicitly check every node against a whitelist of workflow-compatible types. If any unsupported node is found, block the import and surface a clear error in the UI (ImportWorkflowPanel.tsx). For maintainability, keep the allowed-types list in one place and ensure the UI always reflects validation failures.

This will ensure that importing a chatflow DSL into a workflow fails as expected when incompatible nodes are present.

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 6, 2025): <!-- Answer --> The root cause is that the import process does not strictly validate node compatibility between chatflows and workflows. The code recognizes node types and has a list of allowed workflow node types, but the enforcement is incomplete—so incompatible nodes can slip through and be imported. To fix this, update the import logic (in fromChatflowDsl.ts) to explicitly check every node against a whitelist of workflow-compatible types. If any unsupported node is found, block the import and surface a clear error in the UI (ImportWorkflowPanel.tsx). For maintainability, keep the allowed-types list in one place and ensure the UI always reflects validation failures. This will ensure that importing a chatflow DSL into a workflow fails as expected when incompatible nodes are present. <!-- 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/460a7fb0-c802-4228-8f0f-846caa78ed68?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/460a7fb0-c802-4228-8f0f-846caa78ed68?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/460a7fb0-c802-4228-8f0f-846caa78ed68?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/460a7fb0-c802-4228-8f0f-846caa78ed68?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/460a7fb0-c802-4228-8f0f-846caa78ed68?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/460a7fb0-c802-4228-8f0f-846caa78ed68?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/460a7fb0-c802-4228-8f0f-846caa78ed68?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/24883)
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#16601
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?