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

Error when using iteration after upgrading to 1.11.3 #21943

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

Originally created by @AchieSun on GitHub (Jan 28, 2026).

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.11.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Description

After upgrading my local Dify deployment to version 1.11.3, I encounter an error when using the iteration feature. Regardless of what array variable I pass into the iteration, the entire iteration fails with the following error:
[INVALID_ROOT] Root node '1769579512012' must declare execution type 'root'.

However, when I manually pass individual elements from the array directly into the iteration (bypassing the array input), all tools work correctly.

Steps to Reproduce

  1. Upgrade Dify to version 1.11.3
  2. Create a workflow with iteration node
  3. Pass any array variable to the iteration
  4. Execute the workflow

Expected Behavior

Iteration should process each element in the array without errors.

Actual Behavior

Workflow fails with [INVALID_ROOT] Root node '1769579512012' must declare execution type 'root'. error.

Environment

  • Dify version: 1.11.3
  • Deployment: Local

Additional Context

This appears to be a regression introduced in version 1.11.3, as the same workflow worked correctly in previous versions.

✔️ Expected Behavior

iteration run correctly

❌ Actual Behavior

iteration can‘t run

Originally created by @AchieSun on GitHub (Jan 28, 2026). ### 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.11.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce ## Description After upgrading my local Dify deployment to version 1.11.3, I encounter an error when using the iteration feature. Regardless of what array variable I pass into the iteration, the entire iteration fails with the following error: [INVALID_ROOT] Root node '1769579512012' must declare execution type 'root'. However, when I manually pass individual elements from the array directly into the iteration (bypassing the array input), all tools work correctly. ## Steps to Reproduce 1. Upgrade Dify to version 1.11.3 2. Create a workflow with iteration node 3. Pass any array variable to the iteration 4. Execute the workflow ## Expected Behavior Iteration should process each element in the array without errors. ## Actual Behavior Workflow fails with `[INVALID_ROOT] Root node '1769579512012' must declare execution type 'root'.` error. ## Environment - Dify version: 1.11.3 - Deployment: Local ## Additional Context This appears to be a regression introduced in version 1.11.3, as the same workflow worked correctly in previous versions. ### ✔️ Expected Behavior iteration run correctly ### ❌ Actual Behavior iteration can‘t run
yindo added the 🐞 bug label 2026-02-21 20:14:57 -05:00
yindo closed this issue 2026-02-21 20:14:57 -05:00
yindo commented 2026-02-21 20:14:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 28, 2026):

Hi @AchieSun! I'm Dosu and I’m helping the dify team.

This is a known regression in Dify 1.11.3. The error [INVALID_ROOT] Root node ... must declare execution type 'root' happens because the workflow validator now requires the root node of any workflow or subgraph to have its execution type set to root, unless it's a special container entry like ITERATION_START or LOOP_START. When running or debugging an iteration node alone, the validator treats the iteration container node as the root, but its execution type is container, not root, which triggers the error. This stricter validation was introduced in recent versions and did not exist in earlier ones, which is why your workflow used to work as expected.

A fix has already been merged for future versions that allows LOOP and ITERATION container nodes to be valid graph roots, so this error won't occur after you upgrade to a version with that fix (see PR #29680). For now, as a workaround in 1.11.3, run the entire workflow instead of running the iteration node alone—this avoids the error. More details and discussion are available here and here.

There are no required configuration changes or migration steps for this issue; it's a backend validation bug. Watch for the next release with the fix if you need to debug iteration nodes directly.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Jan 28, 2026): <!-- Greeting --> Hi @AchieSun! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This is a known regression in Dify 1.11.3. The error `[INVALID_ROOT] Root node ... must declare execution type 'root'` happens because the workflow validator now requires the root node of any workflow or subgraph to have its execution type set to `root`, unless it's a special container entry like `ITERATION_START` or `LOOP_START`. When running or debugging an iteration node alone, the validator treats the iteration container node as the root, but its execution type is `container`, not `root`, which triggers the error. This stricter validation was introduced in recent versions and did not exist in earlier ones, which is why your workflow used to work as expected. A fix has already been merged for future versions that allows LOOP and ITERATION container nodes to be valid graph roots, so this error won't occur after you upgrade to a version with that fix ([see PR #29680](https://github.com/langgenius/dify/pull/29680)). For now, as a workaround in 1.11.3, run the entire workflow instead of running the iteration node alone—this avoids the error. More details and discussion are available [here](https://github.com/langgenius/dify/issues/28114) and [here](https://github.com/langgenius/dify/issues/30577). There are no required configuration changes or migration steps for this issue; it's a backend validation bug. Watch for the next release with the fix if you need to debug iteration nodes directly. <!-- 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/5a881ab7-e59c-4b03-b68c-ca3ea2587719?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/5a881ab7-e59c-4b03-b68c-ca3ea2587719?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/5a881ab7-e59c-4b03-b68c-ca3ea2587719?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/5a881ab7-e59c-4b03-b68c-ca3ea2587719?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/5a881ab7-e59c-4b03-b68c-ca3ea2587719?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/5a881ab7-e59c-4b03-b68c-ca3ea2587719?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/5a881ab7-e59c-4b03-b68c-ca3ea2587719?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=This%20is%20a%20known%20regression%20in%20Dify%201.11.3.%20The%20error%20%60%5BINVALID_ROOT%5D%20Root%20node%20...%20must%20declare%20execution%20type%20%27root%27%60%20happens%20because%20the%20workflow%20validator%20now%20requires%20the%20root%20node%20of%20any%20workflow%20or%20subgraph%20to%20have%20its%20execution%20type%20set%20to%20%60root%60%2C%20unless%20it%27s%20a%20special%20container%20entry%20like%20%60ITERATION_START%60%20or%20%60LOOP_START%60.%20When%20running%20or%20debugging%20an%20iteration%20node%20alone%2C%20the%20validator%20treats%20the%20iteration%20container%20node%20as%20the%20root%2C%20but%20its%20execution%20type%20is%20%60container%60%2C%20not%20%60root%60%2C%20which%20triggers%20the%20error.%20This%20stricter%20validation%20was%20introduced%20in%20recent%20versions%20and%20did%20not%20exist%20in%20earlier%20ones%2C%20which%20is%20why%20your%20workflow%20used%20to%20work%20as%20expected.%20%0A%0AA%20fix%20has%20already%20been%20merged%20for%20future%20versions%20that%20allows%20LOOP%20and%20ITERATION%20container%20nodes%20to%20be%20valid%20graph%20roots%2C%20so%20this%20error%20won%27t%20occur%20after%20you%20upgrade%20to%20a%20version%20with%20that%20fix%20%28%5Bsee%20PR%20%2329680%5D%28https%3A//github.com/langgenius/dify/pull/29680%29%29.%20For%20now%2C%20as%20a%20workaround%20in%201.11.3%2C%20run%20the%20entire%20workflow%20instead%20of%20running%20the%20iteration%20node%20alone%E2%80%94this%20avoids%20the%20error.%20More%20details%20and%20discussion%20are%20available%20%5Bhere%5D%28https%3A//github.com/langgenius/dify/issues/28114%29%20and%20%5Bhere%5D%28https%3A//github.com/langgenius/dify/issues/30577%29.%0A%0AThere%20are%20no%20required%20configuration%20changes%20or%20migration%20steps%20for%20this%20issue%3B%20it%27s%20a%20backend%20validation%20bug.%20Watch%20for%20the%20next%20release%20with%20the%20fix%20if%20you%20need%20to%20debug%20iteration%20nodes%20directly.)&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/31642)
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#21943
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?