How can different end nodes output the same key variable?
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 24.6k
- Avg merge
- 22h 9m
- Merged PRs (30d)
- 610
Description
### 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.15.0
### Cloud or Self Hosted
Self Hosted (Docker)
### Steps to reproduce
Set two end nodes with the same input key
### ✔️ Expected Behavior
the workflow able to publish
### ❌ Actual Behavior
Error: A variable cannot be duplicated, causing the workflow to be unable to publish
Contributor guide
Research direction
Start by reproducing the issue in the self-hosted Docker deployment with two end nodes using the same input key. Trace the workflow publish validation to determine why duplicate keys are rejected; the work is done when this workflow publishes successfully without breaking duplicate-variable validation elsewhere.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100