Error in FunctionInvoker
See original GitHub issueI have a timer triggered C# function, which has been running successfully for a while but failed last night, but the logs don’t seem to point to an issue with my own code. I manually ran it today and it worked fine. Here’s the output from the failed invocation of the function:
...obs.Script.Description.FunctionInvokerBase.<Invoke>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.WebJobs.Host.Executors.FunctionInvoker`1.<InvokeAsync>d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<InvokeAsync>d__53.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithWatchersAsync>d__3b.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithLoggingAsync>d__36.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.<ExecuteWithLoggingAsync>d__1a.MoveNext()
--- End of inner exception stack trace ---
Any ideas what might cause this, or how I can debug further?
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Class not found: org.springframework.cloud.function. ...
I am using latest version of spring cloud function and trying to run it in AWS lambda. Some how FunctionInvoker class is not...
Read more >Azure function failing with Microsoft.Azure.WebJobs.Host. ...
This is working great but I'm running into a lot of Microsoft.Azure.WebJobs.Host.FunctionInvocationException errors. The error messages are not ...
Read more >Getting error System.UriFormatException in Azure Function ...
Getting below error while executing Service bus trigger Azure function and unable to start Azure Function on Azure portal.
Read more >Resolve "ClassNotFoundExeption" errors from Java ...
Short description. The ClassNotFoundException error occurs when a Java runtime loads a class by its fully qualified name, but doesn't locate the class....
Read more >Sample Error handling and custom http status codes in ...
Sample Error handling and custom http status codes in Spring cloud function + Lambda + gateway ... FunctionInvoker::handleRequest Runtime: java11 CodeUri: ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m guessing the full logs are in Azure Table storage, but would be great to see all the function output in the portal when you look at a failed invocation on the monitor tab. My function starts with a
log.Info
message so the fact I couldn’t see that made me assume it hadn’t got as far as running at all.And BTW the bug was obvious once I knew it was an
IndexOutOfRangeException
- I had a+1
instead of-1
, so thanks again for helping me track down the problem.I figured that as soon as you had the exception type, the fix would likely be pretty obvious 😃 That’s why making sure that information is surfaced is so important.