Run Child Flow - Workflow Reference Name not found

(5) Share

Report

Posted on by santoGD

Hi All,

In my power automate flows, from today, run a child flow always shows error:

'Failed to retrieve dynamic inputs. Error details: 'Parameter "workflowReferenceName" cannot be found for this operation'

This error is showing for all automate flows and all run a child flow component. Also, for my other team mates too, the same error is showing.

What can be the cause of this issue?All the child flows are still there. Please advise

These Flows are available from last 5-6 months and we never seen any error like this and we havenot changed anything.

Thanks

Santo

Categories:

General topics

I have the same question (0)

All responses (8)

Answers (0)

CFernandes 8,482 Most Valuable Professional on at

Like (1)

Report
Copy link

Link copied!

Can you switch to the Old Editor and see if you can reproduce the problem. Check if the connection is correct?

If you are using manual flow, connections are configured as "provided by run only user" so you need to provide fixed connections for all of those connectors.

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!

P.S. take a look at my blog here and like & subscribe to my YouTube Channel thanks.

Was this reply helpful? Yes No
PB-14101904-0 2 on at

Like (1)

Report
Copy link

Link copied!

I too am seeing the same issue over the past 3 days with this message in my flows

Was this reply helpful? Yes No
santoGD 58 on at

Like (1)

Report
Copy link

Link copied!

I have checked with Old designer and not seeing any issues with 'Run a child flow' component.

Regarding:

If you are using manual flow, connections are configured as "provided by run only user" so you need to provide fixed connections for all of those connectors.

we are using Service principal user for last 6 months . No issues happened till yesterday for child flow calls.

Thanks

Was this reply helpful? Yes No
HC Sol 30 on at

Like (1)

Report
Copy link

Link copied!

Hi All

I am geting this to, i have just upgradeed a List and updated my Enviroment Variable to that point to the New List version.

All of my flows that call Manual Triggered flows wont work with "Error details: 'Parameter "workflowReferenceName"".

Note that the actual Manual triggered flows seem to test fine. And i have checked the "Run only users" on all of them.

So im not sure at all what is going on.

Anyone got to the bottom of this?

Was this reply helpful? Yes No
HC Sol 30 on at

Like (1)

Report
Copy link

Link copied!

UPDATE: But no fix, only diagnosis

After investigating it all seems to be centered around the 'Run a child' action. When a My list triggers I attempt to 'Run_a_Child_Flow-_RefGenV2' and I get the following error that my action requires a 'Object' .

Action 'Run_a_Child_Flow-_RefGenV2' failed: The input body for trigger 'manual' of type 'Request' did not match its schema definition. Error details: 'Invalid type. Expected Object but got Integer.'

The Co-Pilot response is:

But this is BS because my manual child flow calls for an Integer ID, always has, always will.

Was this reply helpful? Yes No
Kinson-Lam (WCC) 36 on at

Like (1)

Report
Copy link

Link copied!

I have exactly the same error when opening the flow in New Designer but not in the old designer.

However, my flow is within a Solution, it has to be using New designer.

Any solution yet?

Was this reply helpful? Yes No
HC Sol 30 on at

Like (1)

Report
Copy link

Link copied!

Most of my Manual triggered flows have a power apps 'Respond to a Power App or Flow' action.

Dont know if this is not working beacuse the manual actions work them selves. Its the result being passed back that is the issue.

Is anyone else seeing this?

Was this reply helpful? Yes No
LS-16100948-0 3 on at

Like (1)

Report
Copy link

Link copied!

We are having the same issue.

Old flows, that have not been touched in weeks, work perfectly fine, while new flows, get the following error when we try to run them:

Edit: Turns out this was a non-related issue but we are still getting this message:

Was this reply helpful? Yes No