-
Notifications
You must be signed in to change notification settings - Fork 188
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
The function invocation context is missing the forwarding task property #2481
Comments
@fabiocav No direspect, however your change in patch 4.34.2, commit c7323b4, has changes in the forwarding service and the timeline of the error showing up kinda lines up. :) Thanks for looking at it! Edit: Nevermind, we're running function host 4.34.1.1 which exactly doesn't yet include your fix I mentioned above. |
This happens in our Azure function too. Running net8.0 in isolated worker. Function host is also 4.34.1.1. StackTrace is exactly the same as in the initial post. Our health function looks like this. Nothing special in it.
|
We recently started seeing this in our function app as well. Any solution or reason why this is happening ? |
We have also been seeing this for a just under a week now. If there is a fix, is it possible to get an indication of a rollout timeline? This is a bit of an annoyance for us as it is failing http triggered requests that have otherwise succeeded, causing retries from third parties to those endpoints. |
We are seeing this too, with the most basic 'Ping' function. Sporadically, not for every request. Runtime version 4.34.1.1 - also would like an indication of when the fix will be rolled out. |
We are seeing the same thing as well. The endpoint we are getting these errors on is a vanilla health check endpoint that just returns 200 response, almost identical to the code @cplankl posted. Runtime version - 4.34.1.22669 |
Also seeing this and it's causing issues for alerting. Roughly 1 failure per hour, but still intermittent. 4.34 runtime, dotnet-isolated, net8.0. Please advise or get in a fix for this... |
I'm seeing this problem happen if I add a custom middleware to a basic function. Code to reproduce |
Middleware moved to ConfigureFunctionsWebApplication.
|
@gsayem |
@gsayem
However, This example includes ASP.NET Core integration to improve performance and provide a familiar programming model when your app uses HTTP triggers. If you do not intend to use HTTP triggers, you can replace the call to ConfigureFunctionsWebApplication with a call to ConfigureFunctionsWorkerDefaults. If you do so, you can remove the reference to Microsoft.Azure.Functions.Worker.Extensions.Http.AspNetCore from your project file. However, for the best performance, even for functions with other trigger types, you should keep the FrameworkReference to ASP.NET Core. |
I think yes, also my errors are gone when I moved my middleware. |
This should work, I tried your example and it's working as expected. |
@gsayem I tried out your recommendation. The error has gone away for me now. I don't fully understand the difference between |
"FUNCTIONS_WORKER_RUNTIME": "dotnet-isolated",
ISSUE:
I have 2 functions:
Startup:
When HC Function is executed, the ex is thrown, nevertheless HC returns Healthy.
Message: Exception while executing function: Functions.HealthCheck The function invocation context is missing the forwarding task property.
Please support.
The text was updated successfully, but these errors were encountered: