Message edit & retry attempt rejected by ServiceControl if tried more than once.

[jpalac]

Describe the bug

Description

If a message is retried using the Edit & retry function and fails, the second retry attempt is ignored by ServiceControl.

Expected behavior

The message is submitted for processing each time the user requests it if the message has not yet been processed successfully.

Actual behavior

The message is rejected by ServiceControl as it thinks it's already been processed.

Versions

6.3+

Steps to reproduce

• Send a message to a handler and have it fail.
• From ServicePulse, retry it using the Edit & retry function
• The message will fail again.
• From ServicePulse, retry it again using the Edit & retry function
• ServiceControl will log that it is ignoring the message retry request

Relevant log output

2025-02-25 14:13:39.4122|15|Warn|ServiceControl.Recoverability.Editing.EditHandler|Discarding edit & retry request because the failed message id ef51ad39-404b-d9aa-368d-b4f60162eb29 has already been edited by Message ID fd48c925-04ef-47bf-94b6-b28f00458a8e

Additional Information

ServiceControl only logs a warning about not processing the message but unless the user is looking at the logs they wouldn't know that the message was not actually retried. The ServicePulse UI tells the user that the message was submitted for retry.

Workarounds

Possible solutions

[bartekwasielak]

The Edit & Retry functionality is working as intended. All valid attempts are processed.
There are cases (described in another issue), where the message is ignored, but this is because a message being edited was already edited and retried.