Cannot query suspended workflows

[ZYSpro]

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.

Content

If I use streaming, I abort the call, and subsequently, when I check, the result is always "running"

[dosubot[bot]]

Hi @ZYSpro! I'm Dosu and I’m helping the dify team.

This is a known issue in Dify: when you abort a streaming call (for example, by disconnecting the client), the workflow can get stuck in the "running" state because the main thread handling database updates is killed before it can mark the workflow as stopped or failed. This means you can't query or manage these suspended workflows through the usual APIs, and logging, results, and token tracking are also missing for these runs. The recommended architectural fix is to decouple database operations from the main thread so status updates can still happen even if the client disconnects, but this hasn't been implemented yet see details.

For now, the only workaround is manual intervention: you can update the workflow status directly in the database or use any available admin API endpoints to mark stuck workflows as failed or stopped. If you need to automate this, look for functions in the workflow node execution repository that allow status updates, and script a cleanup for workflows that have been "running" for too long without progress. This issue only affects streaming mode; non-streaming workflows are not impacted.

To reply, just mention @dosu.

---

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