Child flow run only user connections bug ?

[freddo]

Hi folks,

I'd like to setup a child flow to run from the parent one but I am unable to save my parent flow as I get the following erroe: "Update the child flow for action 'Run_a_Child_Flow' to not use 'run)only user' connections.

Problem: I am unable to adapt my connections ...

I am working in the solutions environment.

Any idea ?

Greetz

[Mister_Shaik · Accepted solution]

Hi @freddo ,

In the Run only users section of your child flow, can you check if you have configured it to a set of users? you can try adding/removing the users on child flow and try saving the Parent flow again.

Hope you find this helpful!

Kind Regards,

Shaik Sha
________________________________________________________________________

If I have answered your question, please mark the post as Solved.
If you like my response, please give it a Thumbs Up.

[freddo]

Thank you for your answer Shaik. I was a bit tired and did not realized that I was indeed looking at the parent side. On the child flow I could adapt the connection.

Best regards,

[nmasmo]

@Mister_Shaik  Hello! What if, in the child flow's dashboard, there is now box to edit "Run only users"?

[anacarolinagr]

Hi! Did you ever resolve this? I have the same problem.

[nmasmo]

@anacarolinagr  Haven't resolved this yet. In my case, I had a triple nested power automate flow. A flow inside a flow inside a flow. But once I made it simply a double nested power automate flow, the error went away. Still don't understand why that fixed it or what truly caused the issue. Have you made any progress on this?

[autopower]

@nmasmo I have the same problem now as well and have deeply nested flows in a solution. It came up specifically when I tried to export and import to a new environment. Is it possible that it is a known limitation that deeply nested flows are not supported by Power Automate yet? Have you found anything suggesting this?

[nmasmo]

@autopower 

I have not found anything online suggesting this, but from my personal experience, I've run into issues with it, so I avoid it from now on. 

Perhaps you could have some luck using http triggers to create "nested" flows.

[anacarolinagr]

@nmasmo My problem was that I was using Power Apps Connector instead of Power Apps v2 connector. Unfortunately, I think your problem is different.

[PaPat]

Hi, to solve this issue you have to go to Run only users of your child flow

And change the connection used settings from "Provided by run-only user" to a defined connection as bellow