Power Platform Community Forum Thread Details

I am encountering an error in my Power Automate solution when triggering a child flow from a parent flow.

Error Message:

Action 'Run_a_Child_Flow' has defined a child flow that contains 'run-only user' connections. Update the child flow for action 'Run_a_Child_Flow' to not use 'run-only user' connections.

Steps I Have Already Taken:

I have already followed the standard fix multiple times:

Opened the Child Flow directly from within the Solution (not My Flows).
Navigated to the flow Details Page.
Clicked Edit under the Run only users section in the bottom-right panel.
Changed all connectors from "Provided by run-only user" to "Use this connection ()" and clicked Save.

Despite applying these updates, turning the flows off/on, and re-saving, the parent flow still throws the exact same connection error.

Flow Setup Details:

Location: Both parent and child flows reside in the same Environment Solution.
Child Flow Trigger: Manually trigger a flow (or Power Apps).
Child Flow End Action: Respond to a PowerApp or flow.
Connectors Used in Child Flow: [HTTP Custom Connectors - PowerBi API used in Invoke HTTP pre-authorized.]

Questions for the Community:

Are there specific connectors (or Connection References) that do not honor the "Run only users" embedded connection override?
Is this a caching/sync issue between Connection References inside the solution layer, and how can I force a reset?
Could child actions added inside nested scopes, loops, or condition branches be masking hidden connection references that aren't appearing in the "Run only users" list?

Any insights or advanced workarounds would be hugely appreciated!

Categories:

Using connectors