Skip to main content
Answer

Indicium API error: Action 'GET' not found in 'TaskController'

  • March 21, 2023
  • 4 replies
  • 78 views

Freddy
Forum|alt.badge.img+16
  • Thinkwise Local Partner Brasil

I have a task that uploads a file via API call, after our migration I get the following error:

Action 'GET' not found in 'TaskController'

What does it mean?

2023-03-21T14:43:33.4011841+00:00 0HMP9C9Q1N09M:00000002 [ERR] An unhandled exception occurred while processing the request. (ffba027a)
System.Exception: Action 'GET' not found in 'TaskController'
at Indicium.OData.ODataRouteValueTransformer.getActionDescriptor(String controllerName, String methodName, String httpMethod) in C:\azp\agent\_work\1\s\src\Indicium\OData\ODataRouteValueTransformer.cs:line 344
at Indicium.OData.ODataRouteValueTransformer.fromActionDescriptor(String controllerName, String methodName, String httpMethod) in C:\azp\agent\_work\1\s\src\Indicium\OData\ODataRouteValueTransformer.cs:line 326
at Indicium.OData.ODataRouteValueTransformer.fromActionDescriptor(ODataPath odataPath, HttpContext httpContext) in C:\azp\agent\_work\1\s\src\Indicium\OData\ODataRouteValueTransformer.cs:line 319
at Indicium.OData.ODataRouteValueTransformer.TransformAsync(HttpContext httpContext, RouteValueDictionary values) in C:\azp\agent\_work\1\s\src\Indicium\OData\ODataRouteValueTransformer.cs:line 209
at Microsoft.AspNetCore.Mvc.Routing.DynamicControllerEndpointMatcherPolicy.ApplyAsync(HttpContext httpContext, CandidateSet candidates)
at Microsoft.AspNetCore.Routing.Matching.DfaMatcher.SelectEndpointWithPoliciesAsync(HttpContext httpContext, IEndpointSelectorPolicy[] policies, CandidateSet candidateSet)
at Microsoft.AspNetCore.Routing.EndpointRoutingMiddleware.<Invoke>g__AwaitMatch|8_1(EndpointRoutingMiddleware middleware, HttpContext httpContext, Task matchTask)
at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Session.SessionMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.ResponseCompression.ResponseCompressionMiddleware.InvokeCore(HttpContext context)
at Indicium.Middleware.Security.AuthenticationHeadersMiddleware.InvokeAsync(HttpContext context) in C:\azp\agent\_work\1\s\src\Indicium\Middleware\Authentication\AuthenticationHeadersMiddleware.cs:line 48
at Indicium.Middleware.Security.SecurityHeadersMiddleware.InvokeAsync(HttpContext context, ContentSecurityPolicyBuilder cspBuilder) in C:\azp\agent\_work\1\s\src\Indicium\Middleware\Security\SecurityHeadersMiddleware.cs:line 55
at Indicium.Middleware.Messages.TSFMessagesMiddleware.Invoke(HttpContext context, IRootApplicationLoader rootApplicationLoader, TSFRequestContext requestContext) in C:\azp\agent\_work\1\s\src\Indicium\Middleware\Messages\TSFMessageMiddleware.cs:line 45
at Indicium.Middleware.Telemetry.ServerTimings.ServerTimingsMiddleware.InvokeAsync(HttpContext context, ServerTimingsBuilder serverTimingsBuilder) in C:\azp\agent\_work\1\s\src\Indicium\Middleware\Telemetry\ServerTimings\ServerTimingsMiddleware.cs:line 43
at Indicium.Middleware.ExceptionHandlingMiddleware.Invoke(HttpContext context, TSFRequestContext requestContext) in C:\azp\agent\_work\1\s\src\Indicium\Middleware\ExceptionHandlingMiddleware.cs:line 84

 

Best answer by Anne Buit

Hi Freddy, tasks should be executed via an http POST call. The error that you see in the log is when a valid task is called with a GET or another unsupported http method.

This topic has been closed for replies.

4 replies

Anne Buit
Community Manager
Forum|alt.badge.img+5
  • Community Manager
  • Answer
  • March 21, 2023

Hi Freddy, tasks should be executed via an http POST call. The error that you see in the log is when a valid task is called with a GET or another unsupported http method.


Freddy
Forum|alt.badge.img+16
  • Author
  • Thinkwise Local Partner Brasil
  • March 21, 2023

Hi Freddy, tasks should be executed via an http POST call. The error that you see in the log is when a valid task is called with a GET or another unsupported http method.

But I'm doing a POST call

 


Freddy
Forum|alt.badge.img+16
  • Author
  • Thinkwise Local Partner Brasil
  • March 21, 2023

Hi Freddy, tasks should be executed via an http POST call. The error that you see in the log is when a valid task is called with a GET or another unsupported http method.

Geen idee wat er gebeurt is, maar krijg de melding niet meer. 


Forum|alt.badge.img+4

Hello Freddy,

I have had issues in the past with Insomnia when using the “Duplicate request” feature. After changing the duplicated request and sending it, it would ignore some of the changes and sort of merge them with the original request that you duplicated. This might have been fixed at some point, so updating Insomnia could help with that, if you think that this could be related to your problem.