Event Grid trigger always returns HTTP 202 about azure-functions-eventgrid-extension

[watashiSHUN]

since we are not doing any deployment during build conference, I would say in a month

[paulbatum]

@glaserbeamer Is this on functions V1 or V2?

@watashiSHUN I'm surprised about this reported behavior, considering that we are not doing any internal queuing yet.. any ideas whats up?

[watashiSHUN]

same issue mentioned here: #32

[glaserbeamer]

@paulbatum Thanks for moving the issue here. I believe this is a V1 function.

@watashiSHUN Thanks for the reference and your detailed response there. I can use an HTTP trigger until this changes.

When creating the Event Grid trigger, it directs users here for logging issues: https://github.com/Azure/azure-functions-templates/issues. It may help to link here instead, if possible.

[DiaAWAY]

I see that a fix has already been committed, when can we expect this change to be available?

[jeffhollan]

Just realized this was an issue when I saw latest release. The catch here though is I don't think Event Grid will keep the HTTP connection open for very long - so if my execution lasted 45 seconds I think it would time out and retry? I can check with Event Grid team on how long it will keep an event connection open -- but I suppose the fact that they have the status code drive deadlettering means we are likely doing what event grid expects.

[jeffhollan]

Just kidding - I may be wrong here - looks like we did wait for function to execute before as well? but we'd always return a 202 anyway? Let me know as I think I assumed incorrectly

[msimpsonnz]

I had the same issue with async Tasks and it was down to just not handling the exception, we were calling an external service but silently handling the error

[mishas23]

since we are not doing any deployment during build conference, I would say in a month

I see that this got fixed in V2.0 but not in V1.0. For some reason our service cannot upgrade to .NET core and hence I am stuck with V1.0. Can you please consider the fix in V1.0 as well. Thanks!