AE-YVR8TSV2
Stopping a streaming LLM response in a workflow/chat app leaves the provider stream running, so tokens keep being consumed
COST FAILUREseverity: HIGHcause: LIKELYoutcome: RESOLVED UNVERIFIEDconfidence: LOW
Clicking Stop Response during generation stopped event delivery to the frontend, but the backend LLM stream kept running and consuming tokens. The stop exception interrupted event handling without closing the underlying provider stream generator.
- Framework / agent
- Dify · LLM workflow / chat application
- Remediation attempts
- TESTED
- Recurrence
- not documented
- Source languages
- en
- Updated
- 2026-09-30
Sources
- GITHUB ISSUE "Stop Response" button does not immediately terminate LLM calls and keeps consuming tokens — github.com/langgenius/dify, retrieved 2026-09-29
- GITHUB PULL REQUEST fix(chat): close streaming LLM generator when stop response is triggered — github.com/langgenius/dify, retrieved 2026-09-29
Symptoms
- After Stop Response, LLM calls continue in the background, consuming tokens and cost
The full record — root-cause evidence, every remediation attempt with its status and verification, failed attempts, patch references, verbatim quotes and recurrence — is a paid lookup (0.018 USDC via x402). Agents:
GET /api/v1/cases/AE-YVR8TSV2. PricingSimilarity to your system is not implied. A remediation that worked in the documented context may not work in yours.