langgenius / langgenius/dify

In dify1.15.0 version, when two Human Input nodes are used, the output content is abnormal

Open
#38,824 1 comment 1 reaction 0 assignees View on GitHub
🐞 bug 1.15.0 project#dify
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

I am deploying in an offline docker compose environment, when upgrading the version from dify 1.10.1-fix.1 to 1.15.0,when two Human Input nodes are used, the output content is abnormal?

Image

The Answer node seems to have output content, but it is not displayed on the UI interface:

Image

### ✔️ Expected Behavior

It displays normally on the UI interface

### ❌ Actual Behavior

The Answer node seems to have output content, but it is not displayed on the UI interface:

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the issue in the self-hosted Docker Compose deployment on Dify 1.15.0, using two Human Input nodes and checking the Answer node output. Trace why the output is present but not displayed in the UI; done means the Answer content displays normally after the upgrade.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.