Loyal-Young opened a new issue, #6050: URL: https://github.com/apache/rocketmq-dashboard/issues/6050
### Before Creating the Bug Report - [x] Searched onActiveDeleted and current conversation deletion reports. #5211 handles failed deletion; the remaining race concerns successful deletion after navigation. ### Studio Version rocketmq-studio at 29fe48abc98583cfc77f97188f187cca3ad85dae. ### Runtime Environment Frontend, Windows / Node 24.18.0, deferred deleteConversation response. ### Connected RocketMQ Cluster Not required; the history operation affects AI conversation records. ### Describe the Bug ConversationListPanel.remove captures activeConversationId before awaiting deletion. When a deletion of conversation A succeeds after the user has closed history and opened conversation B, the old callback calls AiPage's onActiveDeleted and navigates B back to /ai. Conversely, deleting B while A is active and opening B before completion does not navigate away from the now-deleted conversation. ### Steps to Reproduce 1. Open history from conversation A and delete A while delaying the response. 2. Close history and navigate to B. 3. Resolve A's deletion; the old completion still fires onActiveDeleted. The reverse case (start deleting B, then navigate to B) misses the required callback. ### What Did You Expect to See? Successful deleted IDs should be compared with the conversation that is active at completion. Closing only the history modal should still allow a successful deletion of the current conversation to navigate away; leaving the AI page entirely should not trigger an old navigation. ### Are You Willing to Submit a Pull Request? Yes; preserve the public modal callback and add lifecycle tests for both navigation directions, modal close, unmount, and failed deletion. ### AI assistance AI assistance was used to trace the callback lifecycle and draft this report. -- 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]
