Self Checks
Dify version
1.14.0-rc1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
- Create a new Workflow application on Dify console.
- Add a
Human Input node into workflow canvas, configure custom form content, approve/reject action buttons, set delivery method to Web App.
- Complete workflow configuration and publish the application.
- 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.
- Call official Open API endpoint
/v1/chat-messages with parameter response_mode=streaming.
- 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"}
Self Checks
Dify version
1.14.0-rc1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Human Inputnode into workflow canvas, configure custom form content, approve/reject action buttons, set delivery method toWeb App.human_input_requiredevent returns complete data payload, includingform_content,form_token,actionsand all form metadata./v1/chat-messageswith parameterresponse_mode=streaming.human_input_requiredevent only contains event name, with completely empty data body.✔️ Expected Behavior
When calling via Open API streaming mode, the returned
human_input_requiredevent 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 triggeredhuman_input_requiredevent 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"}