You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the discussion in #356 and #356, it would be beneficial to introduce the ability to set message headers (application properties) for Azure Service Bus when a message fails. This enhancement would allow users to:
Preserve partial state information in the message headers during failure scenarios (either within the consumer or the consumer error handler).
Ensure that this state is available for subsequent message retries, aiding in implementing consumer idempotency.
This feature would provide greater flexibility and reliability, especially in scenarios where preserving state across retries is critical.
The text was updated successfully, but these errors were encountered:
zarusz
changed the title
[Host.AzureServiceBus] Ability to set header when message has been is failed
[Host.AzureServiceBus] Ability to set header when message has been failed
Jan 1, 2025
Based on the discussion in #356 and #356, it would be beneficial to introduce the ability to set message headers (application properties) for Azure Service Bus when a message fails. This enhancement would allow users to:
This feature would provide greater flexibility and reliability, especially in scenarios where preserving state across retries is critical.
The text was updated successfully, but these errors were encountered: