If a failure returns from the HTTP Service (anything other than Success, e.g. 404 etc) then the Flow fails and doesn't continue. It would be better if it was to continue and then conditions based on the Status Code can be added to determine the next action.
We have huge set of legacy desktop applications which exposes CLI/API. In our business process theses applicaitons are acting a major role. To automate our end to end process, we need to invoke these tools from Flow. With this, we can utilize the flow for automating our end to end manual process.
I can able to write a wrapper service (HTTP / REST) for the CLI or API exposed by the desktop application and run that service as the windows service in each machine. As part of the workflow, If I am able to invoke these services from flow, will be very helpful for us to automate our process.
It would be nice if users can use Flow for Action to create Planner Tasks based on SharePoint List / Office 365 Group List item status or some other Conditions. It will reduce the need for double entry between Planner and SharePoint lists.
Or some reverse Flows, similar to the actions available for Trello and Wonderlist, plus updating a SharePoint List with a card name, or OneNote entry, or ideally Excel - that can be used as a workaround on the missing reporting functionality from Planner.
This would help people staying within Planner instead of using third party apps.
Flow nicely integrates with various email services, I see separate Actions and Triggers for Gmail, Office 365 Outlook, Outlook.com.
All these services follow a similar pattern. They allow emails to be fetched from an inbox and access the Body, Subject, To, CC etc, which is all nice and well. However, what is deparately needed is the ability to get a copy of the full email in MSG or EML format so the entire email can be passed between services so it can be archived or processed further.
I see quite a few people asking for this in the forums and we need it as well so our customers can pass emails (as MSG or EML) into our Flow based PDF Converter.
Most people ask for a very specific implementation (e.g. Store email in SharePoint), but as we already have the facility to create files in SharePoint (and DropBox, OneDrive, Google Drive, Box.com) we just need a generic function in each of the provided email services to 'Get email as MSG'. From here on the MSG can be passed into other services without tying the implementation into a specific service.
There currently are no triggers for Dynamics 365 for Operations and I think they should be driven by Dynamics 365 for Operations Alerts.
In D3FO, Alerts are planned to be implemented (but do not yet exist). I think it makes logical sense to have Flow triggers connect to Dynamics 365 for Operations Alerts (when available). This would allow one trigger to have an incredibly robust set "virtual triggers" without designing multiple triggers in Flow.
The abilities offered with Alerts+Flow Triggers would be a major "wow" factor for customers and would let you Flow on almost anything.