Issue Station
Sign In
Tools hereToolbox

dify - 💡(How to fix) Fix Feature Request: Service API Support for Human Input Node (Workflow Pause/Resume) [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#35556•Fetched 2026-04-25 06:22:32
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
1
Author
scdengscdeng
Participants
crazywoolacrazywoolascdengscdeng
Timeline (top)
labeled ×3closed ×1commented ×1

Fix Action

Fix / Workaround

  1. Workaround: Is there a recommended approach for Service API users who need human-in-the-loop workflows today?
RAW_BUFFERClick to expand / collapse

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

We're integrating Dify into our enterprise automation platform using the Service API to execute workflows that require human approval at critical decision points.

Our Workflow Scenario:

[Start] → [Data Processing] → [Risk Assessment] → [⚠️ HUMAN APPROVAL] → [Execute Action] → [End] (AI Analysis) (Service API)

What Works:

  • ✅ Start workflow via POST /v1/workflows/run
  • ✅ Workflow executes normally until Human Input Node
  • ✅ Workflow pauses correctly (status: PAUSED)
  • ✅ Can query workflow run status via GET /v1/workflows/run/{id}

What's Broken:

  • ❌ Cannot retrieve the human input form (no Service API endpoint)
  • ❌ Cannot submit approval/rejection (no form submission endpoint)
  • ❌ Cannot resume the workflow (no resume mechanism)
  • ⚠️ Workflow stuck forever in PAUSED state
  • ⚠️ No programmatic way to integrate with our approval system (Jira, custom dashboard, etc.)

Impact: We cannot use Human Input Nodes in production workflows accessed via Service API, which defeats the purpose of "human-in-the-loop" AI automation for external integrations.

2. Additional context or comments

Environment

  • Dify Version: 1.13.3+ (with Human Input Node feature)
  • API Type: Service API (/v1/)
  • Workflow Modes: Both WORKFLOW and ADVANCED_CHAT
  • Deployment: Self-hosted (Kubernetes)
  • Database: PostgreSQL

Questions for Dify Team

  1. Roadmap: Is Service API support for Human Input Nodes planned? If yes, what's the timeline?

  2. Priority: How does this rank compared to other feature requests? (We're happy to provide business case data)

  3. Workaround: Is there a recommended approach for Service API users who need human-in-the-loop workflows today?

3. Can you help us with this feature?

  • I am interested in contributing to this feature.

extent analysis

TL;DR

The most likely fix involves waiting for the Dify team to implement Service API support for Human Input Nodes or exploring alternative workarounds such as using a different API or developing a custom integration.

Guidance

  • Review the Dify roadmap and priority list to understand the timeline for Service API support for Human Input Nodes.
  • Explore alternative APIs or integration methods that may support human-in-the-loop workflows, such as using a different endpoint or developing a custom solution.
  • Consider contributing to the development of this feature or providing a business case to prioritize its implementation.
  • Investigate potential workarounds, such as using a third-party service or developing a custom approval system, to integrate with the existing workflow.

Example

No code snippet is provided as the issue is focused on API support and workflow integration rather than a specific code-related problem.

Notes

The solution to this issue is dependent on the Dify team's roadmap and priority list. The availability of Service API support for Human Input Nodes is crucial to resolving this issue.

Recommendation

Apply workaround: Given the current limitations, exploring alternative APIs, integration methods, or developing a custom solution may be the most viable option for achieving human-in-the-loop workflows with the Service API.

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…
#api#latency issue#model loading#dependency error#configuration error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

dify - 💡(How to fix) Fix Feature Request: Service API Support for Human Input Node (Workflow Pause/Resume) [1 comments, 2 participants]