Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Azure pre-compiled Functions not available to Logic Apps

We are utilising visual studio 2017 and azure precompiled functions in VB.NET. All functions run successfully locally using the func.exe CLI tool. We can publish the Function App to Azure where we can see and test within the portal.

The problem exists when we try to use the functions as part of a logic app. We can add an action selecting Azure Functions and can see our function app, but none of the underlying functions are available/missing.

What am i missing?

Edit I am using http triggers and web hooks.

Edit It was indeed the custom routes

like image 700
Dooie Avatar asked Dec 07 '17 12:12

Dooie


2 Answers

I had a similar issue with logic app. some of my HttpTrigger functions worked fine and others not. I figured out that the only difference was the routing. functions that used custom routes did not show up in the logic app action selector. I've just removed the custom routes and everything work fines.

I've openned an issue here :

  • Discover HttpTrigger Functions from Logic App does not work with custom routes

**EDIT: ** Here is the answer from the Azure Team:

This is by design. As Functions with routes as the way the Azure Function is invoked from Logic Apps is via calling an API "list invoke URL." That URL will look something like https://function.azurewebsites.net/api/my/{custom}/route?code=123 and Logic App doesn't have a way to parse the route template. In other words we don't know what is static, and what should be replaced, and don't have a way to "replace" that with the native action.

You can get around it by providing an OpenAPI definition for the function and we will render the card based on the path parameters specified in swagger. Can also not use route if need to show in Logic Apps.

like image 164
Thomas Avatar answered Sep 28 '22 11:09

Thomas


Only functions of type 'Generic Web Hooks' are supported by Logic Apps. You don't state what type you are using, but if you are using 'http trigger' functions, that could be the problem.

like image 35
David Ebbo Avatar answered Sep 28 '22 11:09

David Ebbo