tju-yxq opened a new issue, #3161: URL: https://github.com/apache/rocketmq-dashboard/issues/3161
## Problem DLQ resend endpoints currently report only aggregate counts. `DLQResendResultVO` contains `matched`, `resent`, `failed`, `outcome`, `scanIncomplete`, and `failedQueueCount`, but no per-message failure information. When a resend returns `PARTIAL` or `FAILED`, the operator still has to find the failed message IDs manually. The current response cannot answer the first questions asked during an incident: - which dead-letter messages were not sent? - which target topic did each failed resend use? - why did the individual resend fail (missing target topic, producer send failure, or no resolvable destination)? - were failures omitted from the response because a very large batch exceeded a display limit? The selected-message resend path has the same limitation: if one of the selected messages fails, only `failed=1` is returned. ## Expected behavior - Each failed resend should report a bounded failure entry containing the dead-letter `msgId`, resolved target topic, and a concise reason. - Both time-range resend and selected-message resend should return the same failure-detail structure. - The failure list should be capped (for example 100 entries) and expose whether additional failures were omitted. - Existing aggregate fields and outcome classification should remain unchanged. - The frontend should show the failed message IDs and reasons for `PARTIAL`/`FAILED` results so operators can retry or inspect the affected messages immediately. -- 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]
