Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow uncaught exceptions to "trigger" another function for global exception handling #4459

Open
jeffhollan opened this issue May 16, 2019 · 6 comments

Comments

Projects
None yet
6 participants
@jeffhollan
Copy link
Member

commented May 16, 2019

Both related to this request

https://feedback.azure.com/admin/v3/suggestions/20308660/

And the fact that people today using bindings aren't able to catch an exception from something like an output binding in the context of the language worker.

@jeffhollan jeffhollan added this to the Backlog milestone May 16, 2019

@simonvane

This comment has been minimized.

Copy link

commented May 17, 2019

For what it's worth I really like the asp.net core filter approach to handling exceptions globally though I can see the merit of another function being triggered providing enough context is available to it.

@alexjamesbrown

This comment has been minimized.

@mayoatte

This comment has been minimized.

Copy link

commented May 23, 2019

@alexjamesbrown

Function filters have a pretty big flaw in that you can't modify the output of the function. E.g. in the case of an http triggered function, you can't decide what status code to return based on the exception caught in the filter.

@alexjamesbrown

This comment has been minimized.

Copy link

commented May 23, 2019

@mayoatte * currently have a pretty big flaw
Hopefully this (eventually) gets some traction Azure/azure-webjobs-sdk#1314

... although it's almost 2 years old :(

@mhoeger

This comment has been minimized.

Copy link
Contributor

commented May 28, 2019

@yuka1984

This comment has been minimized.

Copy link

commented Jul 4, 2019

We can consider using Durable Functions if we want to handle errors with functions other than Http Trigger.

But, Http Trigger functions that require synchronization are difficult to use with Durable Functions.

In particular, there are very many scenarios in which the content formed when Http Trigger Functions encounter an exception is returned.

So I want to give priority to the HttpTrigger function to handle global error handling.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.