unbridled-41 opened a new issue, #5964: URL: https://github.com/apache/rocketmq-dashboard/issues/5964
### Studio Version branch: `rocketmq-studio` @ `7e7aa344` ### Runtime Environment Frontend tests: `cd web && npx vitest run src/pages/instance/__tests__/MessagePageAsyncState.test.tsx`. ### Describe the Bug The Trace tab loads a message's trace through a per-message cache, but the manual lookup (查询轨迹) bypasses the cache and stores its result only in the panel state. The next entry into the tab re-reads the cached promise and puts the superseded snapshot back on screen, taking the diagnostics (delivery status, failed-group count, recommendations) with it. ### Steps to Reproduce 1. Open 消息轨迹 (trace A cached and shown). 2. Press 查询轨迹 for the same msgId (fresher trace B shown). 3. Switch to 消息内容 and back: trace A is displayed again. ### What Did You Expect to See? The refreshed trace stays until the message or the trace topic changes. ### What Did You See Instead? The older snapshot returns on a tab click. ### Impact An explicit user action is silently discarded and the panel shows conclusions known to be superseded. ### Acceptance Criteria A manual msgid lookup publishes its result into the same cache entry the tab load uses, with a regression test. **Corresponding PR:** #ISSUEPR# -- 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]
