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
I have an Azure Functions Service Bus trigger throwing an unhandled exception in the code, I was hoping to see a failure, but the request telemetry still shows success=True. Also, it seems like resultCode only applies to HTTP triggers, as it always shows 0 for Service Bus.
In contrast, HttpTrigger correctly sets success:False when an unhandled error occurs and has the right resultCode.
[Function(nameof(SB))]
public async Task Run(
[ServiceBusTrigger("queue", Connection = "ServiceBusConnection")]ServiceBusReceivedMessage message, ServiceBusMessageActions messageActions)
{
_logger.LogInformation("Message ID: {id}", message.MessageId);
// Complete the message
await messageActions.CompleteMessageAsync(message);
//throw new ArgumentNullException("This is a test exception");
}
It is same with EventHub as well,
The text was updated successfully, but these errors were encountered:
The extensions package has no insight nor influence over whether the Functions runtime considers an execution successful or not, it just invokes an executor from the host and observes the outcome. As such, this is something which requires investigation by the Functions host. I've transferred this to the repository where the host is maintained as #11056.
Uh oh!
There was an error while loading. Please reload this page.
I have an Azure Functions Service Bus trigger throwing an unhandled exception in the code, I was hoping to see a failure, but the request telemetry still shows success=True. Also, it seems like resultCode only applies to HTTP triggers, as it always shows 0 for Service Bus.
In contrast, HttpTrigger correctly sets success:False when an unhandled error occurs and has the right resultCode.
It is same with EventHub as well,
The text was updated successfully, but these errors were encountered: