RockteMQ-AI commented on issue #4739: URL: https://github.com/apache/rocketmq-dashboard/issues/4739#issuecomment-5758710352
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified. The analysis is thorough and the root cause is clear: - `Composer.handleSend` clears the draft on send and expects the caller to restore it on rejection - `AiPage.handleSend` only restores the draft when `target === null` (no conversation yet) - `useAiSend.startRun` returns the conversation id regardless of whether the send was admitted, so the restore path never triggers for an existing conversation - A 409 (run already in flight), provider rejection, or early stream failure leaves the composer empty **Impact:** Users lose their draft when the server refuses a send on an existing conversation. Deterministic and reproducible. **Severity:** Medium — data loss (user input), no crash or corruption. A fix PR (#4740) is already available from the reporter. The fix correctly propagates the rejection back through `startRun` and restores the draft in `AiPage.handleSend`. --- *Automated evaluation by RockteMQ-AI* -- 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]
