RockteMQ-AI commented on issue #4614: URL: https://github.com/apache/rocketmq-dashboard/issues/4614#issuecomment-5751644117
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The bug is confirmed. After a page reload during an active AI run, the client reattaches to the live SSE stream but never receives a `run_started` event, so `runIdRef` stays `null`. This makes `stop()` a client-side no-op (it returns early when the run id is null), while the stop button visually appears clickable because `isStreaming` is true but `canStop` is not consumed by the composer's stop-state logic. **Root Cause:** `useAgentRun` only learns the run id from the `run_started` frame; `attach()` discards the run id passed by the caller. On reattach, the replayed events start from `run_started` which is projected as a live event but never delivered to the hook. **Impact:** AI conversation stop functionality is broken after any page reload/reconnect during streaming. **Severity:** Medium — affects UX but the run eventually completes on its own; no data loss. The proposed fix in #4613 (seeding the hook's run id from the id `attach()` already receives) addresses the root cause correctly. --- *Automated evaluation by RocketMQ AI Assistant* -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
