langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Human-computer interaction workflow #14859

New Issue
Open
opened 2026-02-21 19:19:05 -05:00 by yindo · 15 comments
yindo commented 2026-02-21 19:19:05 -05:00
Owner
Copy Link
Copy Source

Originally created by @Adoubf on GitHub (Jun 24, 2025).

Originally assigned to: @crazywoola on GitHub.

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • 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.

I am building a complex workflow in Dify and encountered a significant limitation: the current Workflow system does not support a "pause-and-wait-for-user" mechanism.

In real-world scenarios, it's common to require human confirmation or decision-making at certain points in the process — for example:

  • After retrieving options from an API, wait for the user to select one before continuing;
  • Pause the workflow, ask the user for approval, then proceed based on their input;
  • Temporarily suspend execution and resume only after explicit user interaction.

Currently, the only workaround is splitting the workflow into multiple applications, which breaks continuity and introduces operational complexity. The JustWait node only delays execution for a fixed time but does not truly wait for user interaction.

This limitation significantly reduces the ability to build human-in-the-loop workflows, which are essential for approval flows, guided processes, and interactive agent experiences.

2. Additional context or comments

Proposed solution:

  • Add a User Interaction Node or similar feature to the Workflow editor.

  • When the workflow reaches this node:

    • The system prompts the user with a message and/or options;
    • The workflow pauses;
    • Once the user provides input (confirmation, text, selection), the workflow continues.

Optional features that would enhance usability:

  • Timeout and fallback path if the user does not respond in time;
  • Support for different types of user input (yes/no, selection, free text);
  • API hooks for advanced integrations;
  • Visual indication of the paused state in the Workflow dashboard.

This feature would greatly expand Dify's ability to support practical business workflows that require human decisions within automated processes.

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Adoubf on GitHub (Jun 24, 2025). Originally assigned to: @crazywoola on GitHub. ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] 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. I am building a complex workflow in Dify and encountered a significant limitation: the current Workflow system does not support a "pause-and-wait-for-user" mechanism. In real-world scenarios, it's common to require human confirmation or decision-making at certain points in the process — for example: * After retrieving options from an API, wait for the user to select one before continuing; * Pause the workflow, ask the user for approval, then proceed based on their input; * Temporarily suspend execution and resume only after explicit user interaction. Currently, the only workaround is splitting the workflow into multiple applications, which breaks continuity and introduces operational complexity. The `JustWait` node only delays execution for a fixed time but does not truly wait for user interaction. This limitation significantly reduces the ability to build **human-in-the-loop workflows**, which are essential for approval flows, guided processes, and interactive agent experiences. ### 2. Additional context or comments Proposed solution: * Add a **User Interaction Node** or similar feature to the Workflow editor. * When the workflow reaches this node: * The system prompts the user with a message and/or options; * The workflow pauses; * Once the user provides input (confirmation, text, selection), the workflow continues. Optional features that would enhance usability: * Timeout and fallback path if the user does not respond in time; * Support for different types of user input (yes/no, selection, free text); * API hooks for advanced integrations; * Visual indication of the paused state in the Workflow dashboard. This feature would greatly expand Dify's ability to support practical business workflows that require human decisions within automated processes. ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement🌊 feat:workflow labels 2026-02-21 19:19:05 -05:00
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jun 24, 2025):

We are working on "Human in the loop" already, we will release it in few months.

@crazywoola commented on GitHub (Jun 24, 2025): We are working on "Human in the loop" already, we will release it in few months.
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@Godzilaa commented on GitHub (Jun 29, 2025):

i am interested in contributing to this feature

@Godzilaa commented on GitHub (Jun 29, 2025): i am interested in contributing to this feature
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@zhengboyuan0 commented on GitHub (Jul 30, 2025):

太好了！非常期待！

@zhengboyuan0 commented on GitHub (Jul 30, 2025): 太好了！非常期待！
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@joyoungzhang commented on GitHub (Aug 18, 2025):

When will this feature be completed?

@joyoungzhang commented on GitHub (Aug 18, 2025): When will this feature be completed?
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@porridgeshoes commented on GitHub (Aug 19, 2025):

Can't wait for the human-in-the-loop feature to be released.

@porridgeshoes commented on GitHub (Aug 19, 2025): Can't wait for the human-in-the-loop feature to be released.
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@Razbolt commented on GitHub (Aug 28, 2025):

We all need this feature promptly!

@Razbolt commented on GitHub (Aug 28, 2025): We all need this feature promptly!
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@Mr-greenplus commented on GitHub (Sep 1, 2025):

We all need this feature promptly!!!

@Mr-greenplus commented on GitHub (Sep 1, 2025): We all need this feature promptly!!!
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@Charlottezhuang19 commented on GitHub (Sep 1, 2025):

Hi we really need this feature and it is of such importance.

@Charlottezhuang19 commented on GitHub (Sep 1, 2025): Hi we really need this feature and it is of such importance.
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@caffbyte commented on GitHub (Sep 1, 2025):

I still consider this feature necessary, but in the meantime, is there any existing functionality or workaround that could provide a similar capability?

@caffbyte commented on GitHub (Sep 1, 2025): I still consider this feature necessary, but in the meantime, is there any existing functionality or workaround that could provide a similar capability?
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@Razbolt commented on GitHub (Sep 2, 2025):

I still consider this feature necessary, but in the meantime, is there any existing functionality or workaround that could provide a similar capability?

Yes, actually, there is a single way to do it. To achieve this, you should break the workflows into multiple steps, which means having multiple API keys and app keys. Then, you should fork the web app and define input placeholders in any IDE (e.g., VS Code, Cursor). You define human interaction by yourself within writing code in any language. Unfortunately, this is the only way to do it for now.

@Razbolt commented on GitHub (Sep 2, 2025): > I still consider this feature necessary, but in the meantime, is there any existing functionality or workaround that could provide a similar capability? Yes, actually, there is a single way to do it. To achieve this, you should break the workflows into multiple steps, which means having multiple API keys and app keys. Then, you should fork the web app and define input placeholders in any IDE (e.g., VS Code, Cursor). You define human interaction by yourself within writing code in any language. Unfortunately, this is the only way to do it for now.
yindo commented 2026-02-21 19:19:06 -05:00
Author
Owner
Copy Link
Copy Source

@caffbyte commented on GitHub (Sep 24, 2025):

I’d like to ask if there has been any update on this feature. Sorry to bother you — I just wanted to check in since the timeline has been quite long. @crazywoola

@caffbyte commented on GitHub (Sep 24, 2025): I’d like to ask if there has been any update on this feature. Sorry to bother you — I just wanted to check in since the timeline has been quite long. @crazywoola
yindo commented 2026-02-21 19:19:07 -05:00
Author
Owner
Copy Link
Copy Source

@gaemeg commented on GitHub (Sep 30, 2025):

🚧 Current Limitation in Dify's Workflow System 🧩

Hey Dify-ers! 👋
We wanted to share an important update regarding the current Workflow system in Dify.

🔹 At the moment, it’s not possible to implement a “pause and wait for user” mechanism within Workflows.
This means Dify does not yet support a “pause-and-wait-for-user” step, which is crucial for many real-world use cases, such as:

✅ Approval flows (e.g. “Wait for manager approval”)
✅ Step-by-step guided processes
✅ Interactive agent experiences that rely on user feedback or decisions

💡 In other words, you can’t yet build proper human-in-the-loop workflows, where human interaction is a required and integrated part of the process logic.

👷‍♂️ We know how important this feature is (and how often it’s requested!) to unlock more advanced and intelligent scenarios.
If this is something you’d love to see in Dify, let us know or support the feature request in the #feature-requests channel! ✨

@gaemeg commented on GitHub (Sep 30, 2025): 🚧 Current Limitation in Dify's Workflow System 🧩 Hey Dify-ers! 👋 We wanted to share an important update regarding the current Workflow system in Dify. 🔹 At the moment, it’s not possible to implement a “pause and wait for user” mechanism within Workflows. This means Dify does not yet support a “pause-and-wait-for-user” step, which is crucial for many real-world use cases, such as: ✅ Approval flows (e.g. “Wait for manager approval”) ✅ Step-by-step guided processes ✅ Interactive agent experiences that rely on user feedback or decisions 💡 In other words, you can’t yet build proper human-in-the-loop workflows, where human interaction is a required and integrated part of the process logic. 👷‍♂️ We know how important this feature is (and how often it’s requested!) to unlock more advanced and intelligent scenarios. If this is something you’d love to see in Dify, let us know or support the feature request in the #feature-requests channel! ✨
yindo commented 2026-02-21 19:19:07 -05:00
Author
Owner
Copy Link
Copy Source

@xujialiang commented on GitHub (Dec 28, 2025):

🚧 Current Limitation in Dify's Workflow System 🧩🚧 Dify 工作流程系统的🧩当前限制

Hey Dify-ers! 👋  嘿，Dify 们！👋 We wanted to share an important update regarding the current Workflow system in Dify.我们想分享一个关于 Dify 当前工作流程系统的重要更新。

🔹 At the moment, it’s not possible to implement a “pause and wait for user” mechanism within Workflows.🔹 目前，在工作流程中还无法实现“暂停等待用户”机制。 This means Dify does not yet support a “pause-and-wait-for-user” step, which is crucial for many real-world use cases, such as:这意味着 Dify 尚未支持“暂停等待用户”步骤，而这对许多实际场景至关重要，例如：

✅ Approval flows (e.g. “Wait for manager approval”)✅ 审批流程（例如“等待经理批准”） ✅ Step-by-step guided processes✅ 逐步引导流程 ✅ Interactive agent experiences that rely on user feedback or decisions✅ 依赖用户反馈或决策的互动客服体验

💡 In other words, you can’t yet build proper human-in-the-loop workflows, where human interaction is a required and integrated part of the process logic.💡 换句话说，你还无法构建真正的人工参与工作流程，让人工互动成为流程逻辑中必需且集成的一部分。

👷‍♂️ We know how important this feature is (and how often it’s requested!) to unlock more advanced and intelligent scenarios.👷 ♂️ 我们知道这个功能有多重要（以及它被要求的频率！），对于解锁更高级、更智能的场景来说。 If this is something you’d love to see in Dify, let us know or support the feature request in the #feature-requests channel! ✨如果你希望在 Dify 中看到这个功能，请在 #feature-requests 频道告诉我们或支持这个功能请求！✨

可以用了吗？

@xujialiang commented on GitHub (Dec 28, 2025): > 🚧 Current Limitation in Dify's Workflow System 🧩🚧 Dify 工作流程系统的🧩当前限制 > > Hey Dify-ers! 👋  嘿，Dify 们！👋 We wanted to share an important update regarding the current Workflow system in Dify.我们想分享一个关于 Dify 当前工作流程系统的重要更新。 > > 🔹 At the moment, it’s not possible to implement a “pause and wait for user” mechanism within Workflows.🔹 目前，在工作流程中还无法实现“暂停等待用户”机制。 This means Dify does not yet support a “pause-and-wait-for-user” step, which is crucial for many real-world use cases, such as:这意味着 Dify 尚未支持“暂停等待用户”步骤，而这对许多实际场景至关重要，例如： > > ✅ Approval flows (e.g. “Wait for manager approval”)✅ 审批流程（例如“等待经理批准”） ✅ Step-by-step guided processes✅ 逐步引导流程 ✅ Interactive agent experiences that rely on user feedback or decisions✅ 依赖用户反馈或决策的互动客服体验 > > 💡 In other words, you can’t yet build proper human-in-the-loop workflows, where human interaction is a required and integrated part of the process logic.💡 换句话说，你还无法构建真正的人工参与工作流程，让人工互动成为流程逻辑中必需且集成的一部分。 > > 👷‍♂️ We know how important this feature is (and how often it’s requested!) to unlock more advanced and intelligent scenarios.👷 ♂️ 我们知道这个功能有多重要（以及它被要求的频率！），对于解锁更高级、更智能的场景来说。 If this is something you’d love to see in Dify, let us know or support the feature request in the #feature-requests channel! ✨如果你希望在 Dify 中看到这个功能，请在 #feature-requests 频道告诉我们或支持这个功能请求！✨ 可以用了吗？
yindo commented 2026-02-21 19:19:07 -05:00
Author
Owner
Copy Link
Copy Source

@xu-song commented on GitHub (Jan 4, 2026):

Image Related example in https://flowiseai.com/
@xu-song commented on GitHub (Jan 4, 2026): <img width="2128" height="574" alt="Image" src="https://github.com/user-attachments/assets/1073824f-cd8b-45c3-bf09-d64f3b031ce5" /> Related example in https://flowiseai.com/
yindo commented 2026-02-21 19:19:07 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 4, 2026):

Hi, @Adoubf. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested a "pause-and-wait-for-user" feature in Dify's Workflow system for human-in-the-loop interactions like approvals.
  • The maintainers confirmed this feature is in development with a planned release in a few months.
  • Community members have shown strong interest and urgency for this capability.
  • Current workarounds require manual multi-step workflows and custom coding.
  • A detailed update highlighted limitations and encouraged support in the #feature-requests channel.

Next Steps:

  • Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open.
  • Otherwise, I will automatically close this issue in 15 days.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Feb 4, 2026): Hi, @Adoubf. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested a "pause-and-wait-for-user" feature in Dify's Workflow system for human-in-the-loop interactions like approvals. - The maintainers confirmed this feature is in development with a planned release in a few months. - Community members have shown strong interest and urgency for this capability. - Current workarounds require manual multi-step workflows and custom coding. - A detailed update highlighted limitations and encouraged support in the #feature-requests channel. **Next Steps:** - Please let me know if this issue is still relevant to the latest version of Dify by commenting here to keep the discussion open. - Otherwise, I will automatically close this issue in 15 days. Thanks for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🌊 feat:workflow 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#14859
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?