zmuxuny opened a new issue, #7179: URL: https://github.com/apache/rocketmq-dashboard/issues/7179
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version rocketmq-studio at 127c47b06a268cc74224d5f34c56ec7c36ac0d55 ### Runtime Environment Linux, Node.js 24.19.0, Vitest 4.1.10/jsdom. Reproduced using the real ResourceOperationTimelineModal and Ant Design controls, with only service responses controlled. ### Connected RocketMQ Cluster No live RocketMQ cluster or database is required or contacted. This is frontend recovery from a failed audit-list request. ### Build Toolchain _No response_ ### Describe the Bug A failed resource timeline request replaces the records and pagination with an error saying to try again later, but offers no Retry action. On a later page, the pagination controls are also gone. The operator must change the date filter or close and reopen the timeline; closing unmounts it and loses the selected dates and page. The current resource query cannot simply be retried in place. ### Steps to Reproduce 1. Open a resource timeline from the Audit page. 2. Select a date range and go to page 2 of a result with multiple pages. 3. Make that read fail transiently. The error appears and pagination disappears. 4. Restore the service and try to repeat the same resource/date/page request. There is no retry action; closing and reopening resets the view. The initial read has the same missing recovery action. A controlled regression reaches the error and fails specifically because the Retry button is absent. ### What Did You Expect to See? An in-place Retry action should rerun the same resource type, target, cluster scope (including clusterIdMissing), date range, page and page size. It should show loading during the retry, permit another retry if that fails, and retain the existing protection against responses for an older resource. ### What Did You See Instead? Only the error remains. Current-page navigation is unavailable after a failed page read, and recovery requires changing the query or recreating the modal. ### Additional Context The focused fix adds the existing common.retry action and a reload generation to the local response identity; no new endpoint or translation text. Five new real-AntD tests cover English/Chinese initial recovery, filtered page 2 with missing cluster scope, repeated failure followed by empty success, and a late retry response after a resource change. Exact final tests on unchanged production fail in all five cases at the missing Retry action. Final related suite: 61 tests / 5 files pass; forced TypeScript build, two-file ESLint, Prettier and diff checks pass. Independently reviewed. No full frontend suite, bundle build, backend or live-cluster testing was run. Existing #6051 handles retention shrinking page totals; #6801/#6686 concern date filters/time formats. Neither supplies failed-read retry. ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
