The node is stuck in the running state and cannot proceed.

[Jiixiang]

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.10.1-fix

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

We deploy images via Kubernetes. After the user enters roughly two rounds of inputs, when they attempt the third round of input, the node gets stuck in the Running state and fails to proceed, returning an empty result. However, the status shown in the logs is Success.

✔️ Expected Behavior

We expect the nodes to proceed with normal operation without interruption.

❌ Actual Behavior

In parallel processing scenarios, our nodes will converge on a single node and then enter the conditional judgment node. During this process, some nodes will get stuck and remain in the Running state persistently; however, the status displayed in the logs is Success.

[dosubot]

This issue is likely caused by a missed or blocked node state transition after parallel or conditional (branch) processing. In Dify, when a node succeeds, the event handler should call finish_execution to update the node state from Running to Success and trigger downstream nodes. If this call is missed—due to edge processing issues, branch selection problems, or async timing (especially with Celery workers)—the node can remain stuck in Running state even though logs show Success¹²³⁴.

For troubleshooting:

• Review your workflow for complex parallel/convergent/conditional logic that could cause deadlocks or missed transitions.
• Check Kubernetes pod logs, Celery worker logs, and Dify backend logs for errors or warnings at the time of the hang.
• Make sure resource limits and concurrency settings in your Kubernetes deployment are sufficient.
• If using Celery, confirm all workers are healthy and tasks are not delayed or dropped.
• Try a simplified workflow to see if the issue persists—this can help isolate whether the problem is with workflow complexity or the runtime environment.
• If the problem continues, collect detailed logs and workflow definitions for deeper investigation.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

Footnotes

1. Event handler logic for node state transitions ↩

2. GraphStateManager node execution tracking ↩

3. EdgeProcessor branch/conditional node handling ↩

4. Celery async repository and possible timing issues ↩

[crazywoola]

Please provide an reproduceable DSL :)

[Jiixiang]

Please provide an reproduceable DSL :)请提供可复现的 DSL 连接信息 :)

对话式活动生成20251224（勿动）.yml