mirror of
https://github.com/langgenius/dify.git
synced 2026-10-04 13:47:55 +08:00
run_draft forwarded the pipeline's ``event: error`` frame to the frontend and then dropped it, so the ESQ1-302 launch failure (Graph.init rejected an http-request node before workflow_started) fell into the truncated-stream path and was reported as "running". The handler's unknown-outcome branch then sent the user back to re-run, forever. The loop now keeps the first error frame aside and _finish_run applies one precedence: terminal frame > error frame > nothing. Chatflow emits workflow_finished(failed) AND an error frame for one failure, so the terminal frame must win; a stream that ends with neither still reads as an unknown outcome, never as a fabricated failure. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>