Skip to content

Conversation

@cquirosj
Copy link
Contributor

@cquirosj cquirosj commented Oct 23, 2025

Fixes #5118

RetryAcknowledgementBehavior in NSB core expects a value in both "ServiceControl.Retry.UniqueMessageId" and "ServiceControl.Retry.AcknowledgementQueue" headers in order to dispatch an OutgoingMessage confirming the successful retry

@cquirosj cquirosj force-pushed the ResolvedByEdit branch 2 times, most recently from cec3fad to 7ebe491 Compare October 24, 2025 05:57
Copy link

@bartekwasielak bartekwasielak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I appreciate the changes of the methods' names. This helps with understanding a difference between the business message and the edit request.

}

public Task Announce(MessageContext messageContext)
public Task Announce(string failedMessageId)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This change creates a difference between this Announce and ErrorProcessor.Announce. I know that the latter uses much more information - would it be worth to keep these both consistent?

@bartekwasielak bartekwasielak force-pushed the ResolvedByEdit branch 12 times, most recently from 07c743e to 0c3d770 Compare October 30, 2025 18:43
@bartekwasielak bartekwasielak self-assigned this Oct 31, 2025
@bartekwasielak bartekwasielak force-pushed the ResolvedByEdit branch 3 times, most recently from c9c8baa to b47687e Compare October 31, 2025 16:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Edit and Retry message doesn't trigger MessageFailureResolvedByRetry

3 participants