dify - 💡(How to fix) Fix Workflow Human Input human_input_required event returns empty data in Open API streaming call [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35504Fetched 2026-04-23 07:45:22
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Timeline (top)
labeled ×2commented ×1mentioned ×1subscribed ×1
RAW_BUFFERClick to expand / collapse

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.14.0-rc1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Create a new Workflow application on Dify console.
  2. Add a Human Input node into workflow canvas, configure custom form content, approve/reject action buttons, set delivery method to Web App.
  3. Complete workflow configuration and publish the application.
  4. Test in Dify web frontend preview chat page: the human_input_required event returns complete data payload, including form_content, form_token, actions and all form metadata.
  5. Call official Open API endpoint /v1/chat-messages with parameter response_mode=streaming.
  6. Check the returned SSE streaming response: the human_input_required event only contains event name, with completely empty data body.

✔️ Expected Behavior

When calling via Open API streaming mode, the returned human_input_required event should be completely consistent with the web frontend preview result. It should return full payload data, including form_content, form_token, action button configurations and all original form information, so that external systems can obtain approval information and resume the suspended workflow.

❌ Actual Behavior

When calling Dify Workflow via official Open API streaming interface /v1/chat-messages, the triggered human_input_required event has empty data field. All metadata of Human Input node is missing, including form content, form token, button options. There is no valid information for external approval integration and workflow recovery.

API returned raw data:

{"event":"human_input_required"}

extent analysis

TL;DR

The human_input_required event returned by the Open API endpoint /v1/chat-messages with response_mode=streaming is missing expected metadata, suggesting a potential inconsistency in event handling between the web frontend and API.

Guidance

  • Verify that the Human Input node configuration is correctly set up and published in the workflow application.
  • Check the Dify version (1.14.0-rc1) for any known issues related to the Open API endpoint or event handling.
  • Compare the event handling logic between the web frontend preview and the Open API endpoint to identify potential discrepancies.
  • Test the Open API endpoint with different response_mode parameters to see if the issue is specific to streaming mode.

Example

No code snippet is provided as the issue seems to be related to the API endpoint behavior rather than a specific code implementation.

Notes

The issue might be specific to the self-hosted Docker setup or the 1.14.0-rc1 version. Further investigation is needed to determine the root cause.

Recommendation

Apply workaround: Check the Dify documentation or community forums for any known workarounds or patches related to the Open API endpoint or event handling in version 1.14.0-rc1, as upgrading to a fixed version is not explicitly implied in the issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING