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
We need a way for people to write error handling code for their input/output bindings, for errors that happen outside of their function logic (e.g. when binding fails in our fx code, not user code). Traditionally, our answer to this has been to rely on the inherent trigger restart logic (varies per trigger). E.g. for a queue trigger, if any of the in/out bindings fail, the queue message will be retried after some time.
However, in some cases, users want to be able to write error handling code for their bindings. They can usually do this by binding to an IAsyncCollector/ICollector and wrapping a try/catch around the calls to Add/Flush. However the model isn't consistent across all bindings. Note: we also want a solution that can apply for languages other than C# in Azure Functions scenarios.
Likely related to the Filters feature we've discussed: Azure/azure-webjobs-sdk#980. The reason being, that in order to be able to capture errors in input bindings as well, the error handling needs to be set up before the function is invoked. Initially for handling output binding scenarios, I had considered an model where the user could subscribe an event handler imperatively in their code, e.g. executionContext.OnError += .... Again - we'll need a design that works for Azure Functions non C# languages as well.
The text was updated successfully, but these errors were encountered:
We need a way for people to write error handling code for their input/output bindings, for errors that happen outside of their function logic (e.g. when binding fails in our fx code, not user code). Traditionally, our answer to this has been to rely on the inherent trigger restart logic (varies per trigger). E.g. for a queue trigger, if any of the in/out bindings fail, the queue message will be retried after some time.
However, in some cases, users want to be able to write error handling code for their bindings. They can usually do this by binding to an IAsyncCollector/ICollector and wrapping a try/catch around the calls to Add/Flush. However the model isn't consistent across all bindings. Note: we also want a solution that can apply for languages other than C# in Azure Functions scenarios.
Likely related to the Filters feature we've discussed: Azure/azure-webjobs-sdk#980. The reason being, that in order to be able to capture errors in input bindings as well, the error handling needs to be set up before the function is invoked. Initially for handling output binding scenarios, I had considered an model where the user could subscribe an event handler imperatively in their code, e.g.
executionContext.OnError += ...
. Again - we'll need a design that works for Azure Functions non C# languages as well.The text was updated successfully, but these errors were encountered: