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

Unable to copy/paste nodes into iteration/loop nodes, and copied nodes from them paste outside #19964

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

Originally created by @952446418 on GitHub (Oct 27, 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 was trying to move my pre-built functional workflow nodes into an iteration or loop node to add repeated execution logic. However, when attempting to copy and paste these nodes into the iteration/loop node, the action failed. Moreover, when copying nodes that are inside an iteration/loop node, they get pasted outside of it, so they can’t be directly used within the iteration/loop structure. This leads to a huge amount of redundant work, and the inability to copy nodes properly is very frustrating.

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 @952446418 on GitHub (Oct 27, 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 was trying to move my pre-built functional workflow nodes into an iteration or loop node to add repeated execution logic. However, when attempting to copy and paste these nodes into the iteration/loop node, the action failed. Moreover, when copying nodes that are inside an iteration/loop node, they get pasted outside of it, so they can’t be directly used within the iteration/loop structure. This leads to a huge amount of redundant work, and the inability to copy nodes properly is very frustrating. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [x] I am interested in contributing to this feature.
yindo added the 💪 enhancement🌊 feat:workflow labels 2026-02-21 20:05:09 -05:00
yindo closed this issue 2026-02-21 20:05:09 -05:00
yindo commented 2026-02-21 20:05:09 -05:00
Author
Owner
Copy Link
Copy Source

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

This copy/paste limitation with iteration/loop nodes is a known challenge and has been discussed by other users as well. The good news is that a recent feature implementation now allows you to paste existing nodes (with their configurations and prompts) directly into nested blocks like loops and iterations in the workflow editor, so you no longer need to manually re-add and reconfigure each node. However, there is still a limitation: you cannot nest iteration nodes within other iteration nodes (no re-nesting of nested nodes is allowed) — see the discussion and details here.

If you're interested in contributing, the copy/paste logic is managed in the workflow state store, with special handling for node hierarchy and context. Improvements should focus on how the graph updates and how context is propagated during copy/paste, especially validating the target node type when pasting. The relevant code lives in the workflow store and node management logic in the frontend, particularly under web/app/components/workflow — see the technical notes here.

Let me know if you want more technical pointers or guidance on where to start!

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 (Oct 27, 2025): <!-- Answer --> This copy/paste limitation with iteration/loop nodes is a known challenge and has been discussed by other users as well. The good news is that a recent feature implementation now allows you to paste existing nodes (with their configurations and prompts) directly into nested blocks like loops and iterations in the workflow editor, so you no longer need to manually re-add and reconfigure each node. However, there is still a limitation: you cannot nest iteration nodes within other iteration nodes (no re-nesting of nested nodes is allowed) — see the discussion and details [here](https://github.com/langgenius/dify/issues/24232). If you're interested in contributing, the copy/paste logic is managed in the workflow state store, with special handling for node hierarchy and context. Improvements should focus on how the graph updates and how context is propagated during copy/paste, especially validating the target node type when pasting. The relevant code lives in the workflow store and node management logic in the frontend, particularly under `web/app/components/workflow` — see the technical notes [here](https://github.com/langgenius/dify/blob/dc1ae57dc669f4dbce1daa08b37f2e78068d5074/web/app/components/workflow/store/workflow/index.ts). Let me know if you want more technical pointers or guidance on where to start! <!-- 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/8fad721d-e405-4cea-927b-a1db11d10888?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/8fad721d-e405-4cea-927b-a1db11d10888?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/8fad721d-e405-4cea-927b-a1db11d10888?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/8fad721d-e405-4cea-927b-a1db11d10888?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8fad721d-e405-4cea-927b-a1db11d10888?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/8fad721d-e405-4cea-927b-a1db11d10888?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8fad721d-e405-4cea-927b-a1db11d10888?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/27520)
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 💪 enhancement
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#19964
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?