Getting error calling a child flow

[Jaystechtips]

Hey guys. I've been racking my brain trying to find out a solution for this.

This is my situation.

I would like to trigger another flow after the first one starts. I've been reading this post about using HTTP triggers. https://flow.microsoft.com/en-us/blog/october-updates-for-microsoft-flow/

The problem I have with that is its a premium feature and we would have to pay. I'm currently testing in the Solutions environment but i ran into a problem when connecting the two flows.

Error says: child flows only support embedded connections

Child flow

Child flow

Basically after the approval, call the child flow to send an email notification. Its a simple experiment and then i would build my flow from there.

That part is what i'm stuck with.

[Brad_Groux · Accepted solution]

See the Building the Child Flow section of the Call Child Flows documentation, specifically: 

... if your flow uses anything other than built-in actions or the Common Data Service (current environment) connector, you will need to update the flow to use the connections embedded in the flow. To do this, select the back button to get to the child flow's properties page and then select Edit in the Run only users tile.In the pane that appears, for each connection used in the flow, you will need to select Use this connection (<connection name>) instead of Provided by run-only user.Then, you can select Save. At this time, you cannot pass connections from the parent flow to the child flow. If you do not do this you will receive the following error: _The workflow with id '', name cannot be used as a child workflow because child workflows only support embedded connections.

---

If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!

[efialttes]

Hi!
'Child flows' is a premium improvement of 'nested flows'. Not sure if the original functionality matches your requirements

https://flow.microsoft.com/en-us/blog/build-nested-flows/

Hope this helps

[Jaystechtips]

Hi @efialttes 

Thanks for the reply.

On a related note, about the HTTP connector. This might be the one I need. Though i'm not sure if the company want to pay more unless I give them a pretty convincing reason to buy.

Premium Feature

I do have a related question to this. Don't know if this should be posted as a new thread, but here it goes. 

I already contacted sales about this, but they have yet to reply.

I don't know which Power Automate plan suits us.

I'm the only one that needs to create the flow. The other people just receives email approval and respond to it.

Premium Plan

Thanks for looking into this!

[efialttes]

@Jaystechtips 

This microsoft document should help everybody to understand the in-depth changes in the licenses, flow runs, api calls etc. 

https://go.microsoft.com/fwlink/?LinkId=2085130&clcid=0x409%20

IN my case, the official surce I've just referenced is still confusing when explaining Premium connectors licensing, but in this other unofficial source it is explained the following:

Per Flow and Per User Plans include a variety of data sources called “Connectors.” Microsoft has two tiers of Connectors – Standard and Premium. Both are included with either of the paid plans (Per Flow & Per User), the Dynamics 365 Plan and the PowerApp Plan, but not the Office 365 plans.

Hope this Helps!

[Jaystechtips]

Thanks @efialttes 

I've been reading this and kinda confused. It did not really got an explanation as to what Power Automate Plan should I get.

It did not answer the question I had in my mind still. 

I'm still waiting for the sales rep from Microsoft to reply so I can ask them questions.

I might do some more testing about these premium connectors.

[efialttes]

@Jaystechtips 

I understand your point, the official domument is also confusing for me.

As I mentioned the most clear but unofficial info I found on this topic is the following:

Per Flow and Per User Plans include a variety of data sources called “Connectors.” Microsoft has two tiers of Connectors – Standard and Premium. Both are included with either of the paid plans (Per Flow & Per User), the Dynamics 365 Plan and the PowerApp Plan, but not the Office 365 plans.

http://www.interlink.com/blog/entry/radical-changes-to-microsoft-flow-now-called-power-automate