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

About the userinput.files LEGACY #21574

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

Originally created by @zway823-blip on GitHub (Jan 11, 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

Dify 1.11.2

Cloud or Self Hosted

Cloud

Steps to reproduce

Image Image After creating the start node, the input field in the node will appear as userinput.files LEGACY-Ray, and it cannot be deleted. When running later, an error message will appear requiring me to upload system files. How can I solve this problem

✔️ Expected Behavior

I can delete userinput.files LEGACY-Ray and run it normally

❌ Actual Behavior

No response

Originally created by @zway823-blip on GitHub (Jan 11, 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 Dify 1.11.2 ### Cloud or Self Hosted Cloud ### Steps to reproduce <img width="844" height="1460" alt="Image" src="https://github.com/user-attachments/assets/25dde5e3-daf5-473c-99eb-8eb7e754e3e9" /> <img width="1024" height="619" alt="Image" src="https://github.com/user-attachments/assets/ab01e0a1-c032-43bb-bbb1-bc6205a3266b" /> After creating the start node, the input field in the node will appear as userinput.files LEGACY-Ray, and it cannot be deleted. When running later, an error message will appear requiring me to upload system files. How can I solve this problem ### ✔️ Expected Behavior I can delete userinput.files LEGACY-Ray and run it normally ### ❌ Actual Behavior _No response_
yindo added the 🐞 bugcloud labels 2026-02-21 20:13:16 -05:00
yindo closed this issue 2026-02-21 20:13:16 -05:00
yindo commented 2026-02-21 20:13:16 -05:00
Author
Owner
Copy Link
Copy Source

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

Hi @zway823-blip! I'm Dosu and I’m helping the dify team.

The userinput.files LEGACY-Ray field is a legacy, read-only input that is hardcoded into the workflow start node UI and cannot be deleted or edited through the interface. This is intentional in the current design: the field is always rendered with a "LEGACY" badge and the delete controls are disabled for it. It's not part of your editable workflow variable list, so removing it via the UI isn't possible [source].

If your workflow or backend expects a file upload for this variable and none is provided, you'll get runtime errors like "contents are required." The backend strictly checks for required file input variables and their schema [source].

Workarounds:

  • If your workflow supports code nodes, you can add a code node after the start node to transform or assign file variables as needed.
  • If you can't use code nodes, reference sys.files or userinput.files directly in your LLM node configuration, making sure your API payload matches the expected variable name and schema.

There is currently no way to remove or bypass this legacy field via the UI in Dify v1.11.2 cloud. This issue has not been fixed in recent updates as of the latest available code and issues [source].

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 11, 2026): <!-- Greeting --> Hi @zway823-blip! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> The `userinput.files LEGACY-Ray` field is a legacy, read-only input that is hardcoded into the workflow start node UI and cannot be deleted or edited through the interface. This is intentional in the current design: the field is always rendered with a "LEGACY" badge and the delete controls are disabled for it. It's not part of your editable workflow variable list, so removing it via the UI isn't possible [[source](https://github.com/langgenius/dify/blob/9fad97ec9bc45daf2ac45a514470aa08a7362aaa/web/app/components/workflow/nodes/start/panel.tsx#L22-L88)]. If your workflow or backend expects a file upload for this variable and none is provided, you'll get runtime errors like "contents are required." The backend strictly checks for required file input variables and their schema [[source](https://github.com/langgenius/dify/issues/30050)]. Workarounds: - If your workflow supports code nodes, you can add a code node after the start node to transform or assign file variables as needed. - If you can't use code nodes, reference `sys.files` or `userinput.files` directly in your LLM node configuration, making sure your API payload matches the expected variable name and schema. There is currently no way to remove or bypass this legacy field via the UI in Dify v1.11.2 cloud. This issue has not been fixed in recent updates as of the latest available code and issues [[source](https://github.com/langgenius/dify/blob/9fad97ec9bc45daf2ac45a514470aa08a7362aaa/web/app/components/workflow/nodes/start/panel.tsx#L22-L88)]. <!-- 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/fd64e198-3d35-4a37-ab37-85f76a9234db?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/fd64e198-3d35-4a37-ab37-85f76a9234db?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/fd64e198-3d35-4a37-ab37-85f76a9234db?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/fd64e198-3d35-4a37-ab37-85f76a9234db?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/fd64e198-3d35-4a37-ab37-85f76a9234db?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/fd64e198-3d35-4a37-ab37-85f76a9234db?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/fd64e198-3d35-4a37-ab37-85f76a9234db?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=The%20%60userinput.files%20LEGACY-Ray%60%20field%20is%20a%20legacy%2C%20read-only%20input%20that%20is%20hardcoded%20into%20the%20workflow%20start%20node%20UI%20and%20cannot%20be%20deleted%20or%20edited%20through%20the%20interface.%20This%20is%20intentional%20in%20the%20current%20design%3A%20the%20field%20is%20always%20rendered%20with%20a%20%22LEGACY%22%20badge%20and%20the%20delete%20controls%20are%20disabled%20for%20it.%20It%27s%20not%20part%20of%20your%20editable%20workflow%20variable%20list%2C%20so%20removing%20it%20via%20the%20UI%20isn%27t%20possible%20%5B%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/9fad97ec9bc45daf2ac45a514470aa08a7362aaa/web/app/components/workflow/nodes/start/panel.tsx%23L22-L88%29%5D.%0A%0AIf%20your%20workflow%20or%20backend%20expects%20a%20file%20upload%20for%20this%20variable%20and%20none%20is%20provided%2C%20you%27ll%20get%20runtime%20errors%20like%20%22contents%20are%20required.%22%20The%20backend%20strictly%20checks%20for%20required%20file%20input%20variables%20and%20their%20schema%20%5B%5Bsource%5D%28https%3A//github.com/langgenius/dify/issues/30050%29%5D.%0A%0AWorkarounds%3A%20%20%0A-%20If%20your%20workflow%20supports%20code%20nodes%2C%20you%20can%20add%20a%20code%20node%20after%20the%20start%20node%20to%20transform%20or%20assign%20file%20variables%20as%20needed.%0A-%20If%20you%20can%27t%20use%20code%20nodes%2C%20reference%20%60sys.files%60%20or%20%60userinput.files%60%20directly%20in%20your%20LLM%20node%20configuration%2C%20making%20sure%20your%20API%20payload%20matches%20the%20expected%20variable%20name%20and%20schema.%0A%0AThere%20is%20currently%20no%20way%20to%20remove%20or%20bypass%20this%20legacy%20field%20via%20the%20UI%20in%20Dify%20v1.11.2%20cloud.%20This%20issue%20has%20not%20been%20fixed%20in%20recent%20updates%20as%20of%20the%20latest%20available%20code%20and%20issues%20%5B%5Bsource%5D%28https%3A//github.com/langgenius/dify/blob/9fad97ec9bc45daf2ac45a514470aa08a7362aaa/web/app/components/workflow/nodes/start/panel.tsx%23L22-L88%29%5D.)&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/30835)
yindo commented 2026-02-21 20:13:16 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jan 11, 2026):

This is only for bug report, if you would like to ask a question, please head to Discussions.

@crazywoola commented on GitHub (Jan 11, 2026): 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).
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 cloud 🐞 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#21574
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?