Nice to see that the "singleton" feature has been introduced!
Why not taking it one level further and make the number of allowed concurrent instances configurable?
In this way, we can easily "throttle" the logic apps by configuration in case the backend system cannot handle a high load.99 votes
1. Logic app should report telemetry to a configurable AI instance.
2. There should be a connection and triggers to react and integrate with AI.41 votes
If Logic Apps had support for MSI then we wouldn't have deal with client ids and secrets when communicating with Web App endpoints within the same AAD.39 votes
MSI support for Logic Apps is in progress.
For load balancing or for failover of Logic Apps with request endpoints we recommend using API Management and making the Logic App an API operation. API Management has first class integration with Logic Apps to make it really easy to add a Logic App as a new API operation and API-M has built-in failover capabilities along with custom policies.
Same as the operation Cancel an work flow run(which is avialble today with Rest API or on Portal ), it would be really great and useful if we can suspend and Unsuspend/Resume a work flow run.29 votes
Thanks for the feedback – we will look into this. Any more detail you could provide on the types of scenarios this would enable could enable for you would be great.
I'd like to see native support for Redis Cache in workflow language or in a connector. Native support would be ideal. Looking for ways to eliminate intensive lookups during dynamic routing scenarios.25 votes
Thanks for the idea. Please keep them coming.
allow the degree of parallelism to be set in for-each loop and the splitOn option of a trigger.24 votes
I'd like a keyword to check for a null value inside your message. I have found a way to hack together the current keywords to make something like this: @equals(coalesce(triggerBody()?.prop, 'Fallback42'), 'Fallback42'). But an isNull keyword would be a lot better.16 votes
It would be useful to know if the Logic App run was initiated by a user resubmitting. Currently, with a peek-lock Logic App, the status is always failure on resubmitted runs because the message doesn't exist to complete. If I could know if it was resubmitted I wouldn't try to complete the message.13 votes
Thanks for your suggestion. Keep them coming.
Add VNet support to Logic Apps. Allow Logic Apps to plug into an existing VNet to support network isolation.13 votes
Allow very simple variables to be persisted to enable loading in the next run. For example, I'm reading data from one API doing some data processing and sending to another. There doesn't seem to be a way of storing the last processed item so the next run only selects newer data.13 votes
I'd like the retry policies (https://msdn.microsoft.com/en-us/library/azure/mt643939.aspx) to include support for Exponential backoff similar to what Polly (https://github.com/App-vNext/Polly) provides.
I've posted a SO question w/reason why this would be useful (http://stackoverflow.com/questions/37493871/does-logic-apps-support-exponential-back-off-with-random-delta).13 votes
Thanks for suggestion – we have looked at these patterns often. Keep votes coming
I am calling an AAD authenticated web app through one of my logic apps. I didn't face any issue while making request from logic app to the web app.
But, the authentication information that I passed to the web app from logic app gets visible when navigating to the Outputs Link on all Logic App run blade. Please see the attachment for details.
I would like those sensitive information to be displayed as *sanitized*, which is the case with outputs link available on an action blade.12 votes
Thanks for adding this suggestion.
By default each action comes with a default retry policy (4 retries 20 seconds apart if I'm not wrong), and this policy can be setup manually for each action. It would be great if that could be set up instead as a logic app wide policy. This would be specially useful in synchronous scenarios were we need to remove the retries (or make it smaller) from each action to avoid timeouts - e.g. setup a logic app wide No Retry policy.12 votes
https://flow.microsoft.com/en-us/documentation/customapi-webhooks/ indicates that Flow will delete a webhook everytime you update the trigger within the Flow.
For a variety of business reasons it is desirable to modify the webhook trigger subscription instead of delete it and add anew.
The MSFT API guidelines [https://github.com/Microsoft/api-guidelines/blob/master/Guidelines.md#147-managing-subscriptions-programmatically] @ 14.7.2 indicate service may support updating webhook subscriptions. Our service has done so (out of necessity), however Flow doesn't currently have a way to use it.10 votes
There doesn't appear to be a way to sort any data in a collection/array. For example, I may retrieve a list of files from an sftp server. I would like to process those files in a particular sort order - such as filename or modified date.9 votes
I assume that you are asking for a built-in array sort expression?
As a work around you can call an Azure Function that can sort the array as well.
Would be nice that you can create a generic Logic App and you can decide at runtime what API connection is must use.
As an example: you create one Logic App that sends a message to the file system. Via configuration, you determine at runtime what File System API connection it should use.
This is currently possible with some code-view modifications, but the designer does not support it. This is not a request to dynamically determine the protocol.8 votes
For conditionals it would be very useful to have type checking functions, specifically is_defined when you have irregular data.7 votes
Thanks for your suggestion! Keep them coming.
HTTP Accept-* headers (such as Accept-Encoding) get dropped in Logic Apps.
Those headers seemt ot be often required and this prevents the usage of Logic Apps for many purposes if would otherwise nicely fit.7 votes
As part of the existing timer trigger it would be great if the interval could be set via CRON expressions, similar to how you allow this with Azure Functions.
For example, I have some scenarios when I want a Logic App to execute once per working day (Monday to Friday here) at 9am7 votes
Thanks for your suggestion. I am curious why the current model for creating a scheduled execution isn’t sufficient and a CRON expression would be needed.
- Don't see your idea?