Update the child flow for action 'Run_a_Child_Flow' to not use 'run-only user' connections.

[gjeh]

Hello All,

I'm trying to run a child flow from a flow to achieve impersonation. However I'm receiving the following Error after inseting the 'run a child flow' block  (child flow is complete and finished):

Update the child flow for action 'Run_a_Child_Flow' to not use 'run-only user' connections.

The error is formulated such that I actualy don't have a clue what it is trying to tell me (english isn't my strong suit).

[gjeh · Accepted solution]

I figured out why i was receiving the error, for the child flow i had yet to define the connectors to be used by users.

[Anonymous]

Nice idea but that didn't work for me.

If I find a another solution I'll add here.

[Sympmarc]

In the child flow, you need to change the 'Run only users' settings, which is currently in the bottom right of the flow dashboard.

Click Edit in that section and change the Connections Used from 'Provided by run-only user' to one of the specific user connections.

[Anonymous]

Thanks @Sympmarc !

[VR-Scott]

Hi @Sympmarc,
I have this same issue. I click edit for the run-only users.

Then I change the Connections Used from 'Provided by run-only user' to one of the specific user connections.

 And yet I still get the error in my parent flow, am I missing something?

[pauldeden]

Same here. Not sure why.

[pauldeden]

I had to edit the flow steps and save them again for the parent flow to recognize I had changed the connections. That fixed it for me.

[pageman]

This fixed it for me as well. After setting the run only users I need to edit one of the actions and save. Thanks for posting this solution.

[Anonymous]

Step @pauldeden mentioned should be also marked as an answer. I thought I did all necessary steps and somehow overlooked that I have to save child flow even though I do not any changes to its actions. This is counter intuitive and made me think error resolved itself while I probably saved it unknowingly fixing it.

[Agnius]

Only changing the run-only permissions was not enough for me, either. Had to open the child flow and save it (without making any changes) to make it work.

[Anonymous]

I am facing the above issue, can someone help?

[shreyagg2202]

Can anyone explain why we had to do this kind of change? Suppose there are 2 accounts and any one of them can run this, doesn't the default option of 'run-only user' make more sense in that case rather than every time changing the connection when switching accounts in the same environment and the same same solution? Or am I misunderstanding and missing something here?

[rw_ga]

I dislike this forced configuration too. The parent flow should either pass connection information down or prompt the user when it is kicked off. I have several child flows that are forced to use a specific username/password - connection and it is an issue with some third-party connections in that all responses sent back are to that SPECIFIED username in the connection NOT the initiating user! Its good for some things, but they need to find a way to allow us to 'pass' the connection information down to the child flows. OR is there already a way and I just don't know how? I don't want to create identical flows multiple times just to allow the initiating user to use their provided connection.

[autopower]

How are the embedded details propagated to the production environment when a solution is packaged as a managed solution and deployed there? Do I need to keep the original connection intact in my developer environment or is it somehow exported within the managed solution to the next environment? Do you know @rw_ga?

[rw_ga]

@autopower 

Sorry, I don't know.