89799969 opened a new pull request, #4384: URL: https://github.com/apache/rocketmq-dashboard/pull/4384
Fixes #3561. ## Problem The Notification Deliveries page only retries FAILED rows loaded on the **current page**. After a webhook or SMTP outage, hundreds of deliveries can be FAILED at once while the page size is 20, so the operator has to page through the feed and retry each page separately. ## Change - Add `POST /api/system-alerts/deliveries/retry-filtered` that selects FAILED deliveries matching the optional `channel` / `instanceId` filters, ordered by delivery id, bounded to `limit` (default 100, valid 1–100). - Reuse the existing per-delivery retry path (`retryFailedDelivery` → status reset + audit) and the existing bulk result envelope. - Add a "Retry matching failures" action on the deliveries page that uses the current channel/instance filters. The current-page retry stays unchanged. - Empty match short-circuits without touching the outbox. ## Verification ```bash cd server && mvn -B -ntp test -Dtest=NotificationOutboxServiceTest cd web && npm test -- --run src/pages/ops/__tests__/NotificationDeliveriesPage.test.tsx ``` - Java: 28/28 passed, including the three new cases (filtered id-order retry, limit bounds, empty short-circuit). - Frontend: 4/4 passed, including `retries every failed delivery matching the current filters`. -- 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]
