Aias00 opened a new issue, #2014: URL: https://github.com/apache/rocketmq-dashboard/issues/2014
## Problem After `clearAcknowledgedAlerts()` succeeds, the System Alerts page only filters rows that were already marked `acknowledged` in its local state. That local snapshot may be stale. If another session acknowledges an additional alert after this page loaded, the backend clear operation deletes both the locally acknowledged alert and the newly acknowledged alert, while the page removes only the first one. ## Reproduction 1. Load alerts A (acknowledged) and B (unacknowledged) in the page. 2. In another session, acknowledge B. 3. Click **Clear acknowledged** on the original page. 4. The backend deletes A and B. The current page filters only local `acknowledged` rows, so B remains visible even though it no longer exists on the server. ## Expected behavior - After a successful clear operation, reload the canonical server alert list. - Do not report the clear itself as failed if only the follow-up refresh fails. - Keep a safe local fallback and show an actionable refresh warning. - Add focused frontend regression coverage for stale local acknowledgement state. ## Scope System Alerts page state reconciliation and tests only. ## Track Track 1 / AI-Native unified control plane. -- 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]
