yuluo-yx opened a new issue, #2691: URL: https://github.com/apache/rocketmq-dashboard/issues/2691
## Problem\n\nThe Message Explorer keeps view state that no longer belongs to the current user action:\n\n1. Reset clears rows but leaves the previous total, page, and scan-truncation warning visible.\n2. Changing the query mode can leave rows from the previous mode on screen, and an in-flight response from that mode can restore them later.\n3. Opening the normal message-content detail immediately requests trace data even when the Trace tab is never used.\n\n## Reproduction\n\n- Run a paginated query that reports a total above one page and resultMayBeTruncated=true, then press Reset.\n- Start a controlled pending query, change from Topic to Message Key mode, and resolve the old request.\n- Open a message through the Detail action and observe a trace request before selecting the Trace tab.\n\n## Expected behavior\n\nReset and query-mode changes should invalidate the prior request and clear all result metadata. Message traces should load only when the Trace tab is first opened, and the same message trace should not be fetched repeatedly during the page lifecycle.\n\n## Scope\n\nKeep the change within the Message Explorer page and focused frontend regression tests. Preserve the existing request-generation ownership behavior for late query and trace responses.\n\n## Evidence\n\nVerified on rocketmq-studio at 899561e56c50d3356cd32caa88f08d80e469eed1. -- 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]
