This feature would be fantastic for creating a modular environment. The passing of parameters between flows and essentially creating the ability to make functions would make flows an irreplacable asset to my work.
This item was part of the October 2019 release : https://flow.microsoft.com/blog/october-updates-for-microsoft-flow/
@bosteelsd - Yes this will be available within the next month.
@Stephen great to hear this is coming so soon, as the change of the HTTP and HTTP Webhook to premium had us concerned. Are you able to confirm what licensing will be required to call a nested flow please? Also, speaking of WebHooks: our team has just been looking at changing a bunch of HTTP calls to WebHooks to avoid problems with the calls to the subflows timing out after 2 minutes. Can you advise how the new subflow calling mechanism would cater for longer-running subflows i.e. that need to be assynchronous calls? Finally, will the subflow run in the user context of the calling flow? Thank you!
@Stephen Any update on this? I could really use this feature for a couple of projects we have in development?
I'm at Ignite this week, and I just asked the Power Automate engineers at the Expo about this feature. I was told that it would only be made available within Flow Solutions. If this indeed the case, that would be very disappointing news given the limitations of Solutions (e.g. "Flows that connect to SharePoint are not available in solutions.").
@Stephen, any chance you can confirm that this is only going to be available within Solutions?
I am also interested in an update. We're coming up on two months since the message that "Yes this will be available within the next month.", and the 2/1/2020 cut over of the HTTP webhook to premium is coming up fast.
This is about to be marked as completed based on the announcement from yesterday:
I would argue that this does not meet the needs of the community because of the crazy limitations of the Solutions architecture. Almost all of our process automations use SharePoint and since Solutions doesn't support Flows that connect to SharePoint, this is yet another feature provides us almost no value.
@Stephen If you want people to adopt Solutions and subsequently use these new features, I would recommend you find a way to remove the limitations currently imposed on Solutions. Otherwise you'll end up with people spinning up yet another suggestion to implement this feature but in a way that meets the needs of the community (similar to what happened with this idea for organizing Flows).
Any update on this one? I found out that our approval process takes more than 30 days. So I need to break down the big flow into several flows.
I found a solution using HTTPS but you have to pay for the premium features. Do you have any solution to this one?
Another requirement could be, to wait until the triggered Flow passes back some output. Means "wait for end of Flow"
yes - it's a "must have" to wait until a triggered Flow finished and passes back some variables
This has been requested 3 years ago... What's going on? It's massive blocker...