An Azure service that provides an event-driven serverless compute platform.
have a look at my answer on the SO
Thanks
Roman
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I have an event grid and I have a subscription for certain events to be delivered to a function app as an "EventGridTrigger". I have read this page https://learn.microsoft.com/en-us/azure/event-grid/delivery-and-retry#message-delivery-status but I have some doubts about error handling
There are certain HTTP status codes that will cause the grid to dead-letter the event or to retry delivery, but I haven't found exactly how this works with function apps. When the event grid sends a new event to a function app and the function app instance is successfully started, is the message considered successfully delivered then? Or is the message considered delivered when the function app successfully ends its execution? Imagine that for whatever reason I want the message to be "rejected" so that the event grid retries the delivery some time later, how would I do that?
An Azure service that provides an event-driven serverless compute platform.
An Azure service that enables bidirectional communication between internet of things (IoT) devices and applications.
An Azure event routing service designed for high availability, consistent performance, and dynamic scale.
@Eugeniu Nicolaescu Looks like there is an open issue to address this feedback. In the meantime, the recommended approach is to use a HTTP Triggered Function instead. There is a feedback request for the same that you could up vote for it gain more traction.
This doc about receiving events to an HTTP endpoint covers how this can be setup for the same.