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
Is your feature related to a problem? Please describe.
The number of immediate processing failures is tracked per physical endpoint deployed. This means the actual number of immediate processing failures can exceed the limit before delayed processing kicks in. This can also lead to increased cost.
Describe the requested feature
The ApproximateReceiveCount attribute could be used as the number immediate processing failures passed to the ErrorContext.
I think it starts at 1, so subtract 0 (with a floor of 0) to compute the number of immediate processing failures.
This could be an opt-in setting for now, or perhaps the default behavior in a major upgrade.
Describe alternatives you've considered
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Describe the feature.
Is your feature related to a problem? Please describe.
The number of immediate processing failures is tracked per physical endpoint deployed. This means the actual number of immediate processing failures can exceed the limit before delayed processing kicks in. This can also lead to increased cost.
Describe the requested feature
The
ApproximateReceiveCount
attribute could be used as the number immediate processing failures passed to theErrorContext
.I think it starts at 1, so subtract 0 (with a floor of 0) to compute the number of immediate processing failures.
This could be an opt-in setting for now, or perhaps the default behavior in a major upgrade.
Describe alternatives you've considered
Additional Context
No response
The text was updated successfully, but these errors were encountered: