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
I am trying to use the WebJobs SDK with the below configuration to run Integration Test for Azure Activity and Durable functions(v4, .Net6.0) as done here but running into the below exception .
Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexingException : Error indexing method 'ForceRefreshTrigger'
---- System.InvalidOperationException : Functions must return Task or void, have a binding attribute for the return value, or be triggered by a binding that natively supports return values.
When I change the Function return type to something different from IActionResult the Indexing seem to work without issues so I was wondering if this is the issue but it works using the Azure Functions SDK when I ran the same set of functions in Visual Studio(Azure Function Core Tools).
I also observed that when I remove the [DurableClient] IDurableOrchestrationClient durableClient, the function indexing also does not throw the above exception. So I am not sure what the root cause of this problem is looking at these 2 anomalies.
Provide the steps required to reproduce the problem
Create HttpTriggered or TimerTriggered function with the signature similar to the above.
Setup a WebJobs host builder configuration above
Expected behavior
The WebJobs SDK should run the Functions successfully
Actual behavior
Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexingException : Error indexing method 'ForceRefreshTrigger'
---- System.InvalidOperationException : Functions must return Task or void, have a binding attribute for the return value, or be triggered by a binding that natively supports return values.
Known workarounds
Change the return type but this would not work for my scenario as we have lots of functions with similar signature that we want to run Integration Test on.
Related information
Provide any related information
Package version
Microsoft.Azure.WebJobs.Extensions: 3.0.6
Azure Function: v4
Links to source
The text was updated successfully, but these errors were encountered:
I am trying to use the WebJobs SDK with the below configuration to run Integration Test for Azure Activity and Durable functions(v4, .Net6.0) as done here but running into the below exception .
Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexingException : Error indexing method 'ForceRefreshTrigger'
---- System.InvalidOperationException : Functions must return Task or void, have a binding attribute for the return value, or be triggered by a binding that natively supports return values.
When I change the Function return type to something different from IActionResult the Indexing seem to work without issues so I was wondering if this is the issue but it works using the Azure Functions SDK when I ran the same set of functions in Visual Studio(Azure Function Core Tools).
I also observed that when I remove the [DurableClient] IDurableOrchestrationClient durableClient, the function indexing also does not throw the above exception. So I am not sure what the root cause of this problem is looking at these 2 anomalies.
Repro steps
Provide the steps required to reproduce the problem
Create HttpTriggered or TimerTriggered function with the signature similar to the above.
Setup a WebJobs host builder configuration above
Expected behavior
The WebJobs SDK should run the Functions successfully
Actual behavior
Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexingException : Error indexing method 'ForceRefreshTrigger'
---- System.InvalidOperationException : Functions must return Task or void, have a binding attribute for the return value, or be triggered by a binding that natively supports return values.
Known workarounds
Change the return type but this would not work for my scenario as we have lots of functions with similar signature that we want to run Integration Test on.
Related information
Provide any related information
Microsoft.Azure.WebJobs.Extensions: 3.0.6
Azure Function: v4
The text was updated successfully, but these errors were encountered: