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

TOOL: Impossible to bind dynamic value in input type: Select #15572

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

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

Cloud or Self Hosted

Cloud

Steps to reproduce

create a workflow that has a select input
make a tool from the workflow
use the tool in another workflow
attempt to bind a variable

Numeric inputs will show a selector for dynamic (variable) / manual (constant) even if in the workflow as tool configuration, the setting was "parameterized"
Strings will show the variable picker respecting workflow as tool configuration
Selects will show a manual (constant) value picker, not the variable input (except tools that were setup in the previous versions. that will retain the variable selector, until you select a value from the constant select dropdown)

✔️ Expected Behavior

It should be possible to bind a variable to a tool input.
Tools created before recent updates display the bound variable, but if removed the input will revert to a constant type input

Image

❌ Actual Behavior

In newly created tools, variables cannot be bound, and the select input is treated as a constant value
Image

In previously created tools there are 2 input methods
Image

But the variable one will go away if you select something in the manual one
Image

And it won't come back
Image

Originally created by @DavideDelbianco on GitHub (Jul 22, 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.1 ### Cloud or Self Hosted Cloud ### Steps to reproduce create a workflow that has a select input make a tool from the workflow use the tool in another workflow attempt to bind a variable Numeric inputs will show a selector for dynamic (variable) / manual (constant) even if in the workflow as tool configuration, the setting was "parameterized" Strings will show the variable picker respecting workflow as tool configuration Selects will show a manual (constant) value picker, not the variable input (except tools that were setup in the previous versions. that will retain the variable selector, until you select a value from the constant select dropdown) ### ✔️ Expected Behavior It should be possible to bind a variable to a tool input. Tools created before recent updates display the bound variable, but if removed the input will revert to a constant type input <img width="609" height="681" alt="Image" src="https://github.com/user-attachments/assets/488b63a0-2e45-4316-9177-32179f3568c5" /> ### ❌ Actual Behavior In newly created tools, variables cannot be bound, and the select input is treated as a constant value <img width="695" height="393" alt="Image" src="https://github.com/user-attachments/assets/4be30f45-2f7a-4051-b298-8749fe1a3187" /> In previously created tools there are 2 input methods <img width="612" height="201" alt="Image" src="https://github.com/user-attachments/assets/6d9c37c3-5a67-4c49-86aa-838824531331" /> But the variable one will go away if you select something in the manual one <img width="601" height="307" alt="Image" src="https://github.com/user-attachments/assets/7ed6b95e-5d7f-4de1-ac58-42f435d005c5" /> And it won't come back <img width="602" height="151" alt="Image" src="https://github.com/user-attachments/assets/0809cffb-d427-46e5-bf3b-61c744ef059a" />
yindo added the 🐞 bug label 2026-02-21 19:22:21 -05:00
yindo closed this issue 2026-02-21 19:22:22 -05:00
yindo commented 2026-02-21 19:22:22 -05:00
Author
Owner
Copy Link
Copy Source

@ss1127201970 commented on GitHub (Jul 27, 2025):

same issue.

@ss1127201970 commented on GitHub (Jul 27, 2025): same issue.
yindo commented 2026-02-21 19:22:22 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Aug 5, 2025):

@crazywoola it's becoming a major pain to manually edit workflow DSL. This a major breaking change (bug) introduced with 1.7 that makes tools with select input unusable. Anyone willing to fix it?

@DavideDelbianco commented on GitHub (Aug 5, 2025): @crazywoola it's becoming a major pain to manually edit workflow DSL. This a major breaking change (bug) introduced with 1.7 that makes tools with select input unusable. Anyone willing to fix it?
yindo commented 2026-02-21 19:22:22 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Aug 22, 2025):

@crazywoola pinging again because it's been 1 month that a breaking change keeps on being live.
Dynamic selects are broken...

@DavideDelbianco commented on GitHub (Aug 22, 2025): @crazywoola pinging again because it's been 1 month that a breaking change keeps on being live. Dynamic selects are broken...
yindo commented 2026-02-21 19:22:22 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Aug 31, 2025):

Day 40: the bug is still strong, the team has not found a medicine

@DavideDelbianco commented on GitHub (Aug 31, 2025): Day 40: the bug is still strong, the team has not found a medicine
yindo commented 2026-02-21 19:22:22 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 1, 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.1 cloud, newly created tools with select inputs no longer support binding dynamic variables, only constants.
  • Older tools lose variable binding once a constant is selected, causing a major usability issue.
  • Multiple reminders were sent to maintainer @crazywoola over a month without resolution.
  • Another user, ss1127201970, confirmed experiencing the same problem.
  • The issue remains unresolved and continues to impact workflow significantly.

Next Steps:

  • Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, I will automatically close this issue in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Oct 1, 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.1 cloud, newly created tools with select inputs no longer support binding dynamic variables, only constants. - Older tools lose variable binding once a constant is selected, causing a major usability issue. - Multiple reminders were sent to maintainer @crazywoola over a month without resolution. - Another user, ss1127201970, confirmed experiencing the same problem. - The issue remains unresolved and continues to impact workflow significantly. **Next Steps:** - Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open. - Otherwise, I will automatically close this issue in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 19:22:22 -05:00
Author
Owner
Copy Link
Copy Source

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

resolved in 1.9.1

@DavideDelbianco commented on GitHub (Oct 8, 2025): resolved in 1.9.1
yindo commented 2026-02-21 19:22:23 -05:00
Author
Owner
Copy Link
Copy Source

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

Thank you for your contribution and for closing the issue, DavideDelbianco! We appreciate your help in improving Dify.

@dosubot[bot] commented on GitHub (Oct 8, 2025): Thank you for your contribution and for closing the issue, DavideDelbianco! We appreciate your help in improving Dify.
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#15572
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?