Webhook Trigger: longer-running workflows (Agent + LLM chains) fail silently on cold/unattended production requests, but succeed reliably when actively monitored via debug URL + Test Run

未关闭
#42,539 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
领域
ai, api, backend

调研方向

Reproduce the workflow with the main webhook URL while comparing a cold request against the debug URL used in a live Test Run session. Check whether the longer Agent and LLM chain appears in the Logs tab and delivers the Gmail message when unattended; done means cold production requests execute fully and reliably.

由索引模型根据 Issue 内容生成。

描述

🐞 bug
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

Dify Cloud (dify.ai hosted)

Cloud or Self Hosted

Cloud

Steps to reproduce
  1. Build a Workflow app: Webhook Trigger → Agent (with a tool, e.g. web search) → LLM (formatting) → Send Gmail Message
  2. Publish the app
  3. WITHOUT opening a Test Run / listening session, send a POST request directly to the main webhook URL (via an external tool, e.g. ReqBin) with valid JSON matching the configured Request Body Parameters
  4. Wait several minutes
  5. Check the app's Logs tab and the destination inbox
✔️ Expected Behavior

The workflow should execute fully and reliably in the background, regardless of whether anyone is actively watching the app in the Dify editor — this is the basic requirement for any real production webhook (e.g. a live website contact form).

❌ Actual Behavior

The cold/unattended request returns a "success" response, but no execution appears in the Logs tab, and no downstream action (e.g. the email) occurs — tested twice, consistently, with waits of several minutes each time.

By contrast, the exact same app, using the special "debug" webhook URL while actively in a live "Test Run → Listening..." session in the Dify editor, executes successfully every time, with all nodes completing and the final email delivered.

A separate, simpler test app (Webhook Trigger → single Gmail node only, near-instant execution) DID succeed reliably even cold/unattended, without any listening session. This suggests the issue may be specific to longer-running chains (e.g. those involving an Agent doing web research), possibly a timeout on unattended/background execution that doesn't apply while a live editor session is open.

主要语言
TypeScript
星标
157k
派生
24.7k
平均合并
22 小时 32 分钟
30 天内合并 PR
611

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

langgenius/dify 的其他 Issue

查看 langgenius/dify 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。