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
As a Function Developer
In order to monitor failures
I need to exit a function with different exit codes
and to control whether a failing message is retried or dead-lettered
Expected behavior
Temporary Failure
Given V.2 Service Bus Trigger
When the client function throws an temporary execution error
Then the message should be retried
Actual behavior
Given V.2 Service Bus Trigger
When the client function throws any exception
Then the function host is restarted
And the telemetry is not sent to AppInsights
Known workarounds
No known workarounds.
The text was updated successfully, but these errors were encountered:
This is a distinct use case from #2087 and specifically relates to triggering a retry - whereas the other issue is specifically regarding signifying a message that should not be re-tried.
As a Function Developer
In order to monitor failures
I need to exit a function with different exit codes
and to control whether a failing message is retried or dead-lettered
Expected behavior
Temporary Failure
Actual behavior
Known workarounds
No known workarounds.
The text was updated successfully, but these errors were encountered: