Unanswered

power automate connector 'create flow' failure: 'OpenApiConnection' should not have the property 'authentication'

(1) Share

Report

Posted on by MichelH

401

I have build a flow that could create a new flow using the 'Create flow' connector.
It uses the flow definition and connection reference, I obtain from a 'Get flow' connector.

I used an excellent tutorial from @JohnLiu to do this.

At the moment when I build the flow, the connector was represented using this icon.

Last week I changed the 'power automate' connection to our service account and then the icon of the connector changed to this:

Now with the very same flow where I get my definition from a 'Get flow', the creation fails.

Flow save failed with code 'WorkflowRunActionInputsInvalidProperty' and message 'The 'inputs' of workflow run action 'Create_Flow' of type 'OpenApiConnection' should not have the property 'authentication'.'.

I believe the previous version of the connector was:

releases/v1.0.1404\\1.0.1404.2172

The new version is:

releases/v1.0.1405\\1.0.1405.2174

Does anyone have an idea where I can find, what is changed and updated in this version of the connector?

Thanks,

Michel

Categories:

Building flows

I have the same question (0)

All responses (7)

Answers (0)

DavidAKlein 2 on at

Like (0)

Report

This breaks on several fronts - Get File Properties, Approvals. It renders the update flow and create flow power automate management actions unusable.

Would it be possible to get an update on this?

Regards,

David

Was this reply helpful? Yes No
pawanjajoo 191 on at

Like (0)

Report

I am facing similar issue with Window Mail Notification action. I have tried creating a new connection, deleted and recreated the connection but to no avail. One thing that I have noticed though is that the "Create Flow" actions works for simple Flow Definitions which does not have branches and multiple if-else or switch-case conditions. Not sure if there is any limitation or bug with the Create Flow action on using complex Flow Definitions. Any help in this regard will be greatly appreaciated.

Regards,
Pawan

Was this reply helpful? Yes No
KRademacher 16 on at

Like (1)

Report

I ran into the same error, and after quite a lot of trial-and-error, I managed to find a solution that worked for me.
What I did, is that I took the connection references of the retrieved flow, and copied them to the new flow.

The retrieved flow:
Connection References of the retrieved flow
And inserted into the new flow:
The settings of the new flow
And this worked! You could make these dynamic, but I know that the connections are not going to change in my case. And be sure to use the same account for the connections in both flows. I don't know for certain, but that could also cause some issues.

I hope this will work for you!

Kevin.

Was this reply helpful? Yes No
MichelH 401 on at

Like (0)

Report

Bedankt Kevin,

I will try this at my earliest convenience.

Br,
Michel

Was this reply helpful? Yes No
fraenK 2,125 on at

Like (0)

Report

Came across the same issue with "HTML to Text conversion" and "Notification to mobile phone" but the workaround from @KRademacher doesn't work for me. Any other ideas how to solve this?

Was this reply helpful? Yes No
marcelosegura 7 on at

Like (0)

Report

Hi all,

Kevins solution seems to work ! Just for simplicity collect definition + ConnectionReferences as outputs of the 'GetFlow' action . Then plug both outputs to the respective inputs of 'Create Flow' connector . .... a bit late reply but hopefully works

Was this reply helpful? Yes No
Stej 22 on at

Like (1)

Report

Here is a workaround that worked for me:
https://blog.atwork.at/post/backup-and-restore-a-flow-with-another-flow

Was this reply helpful? Yes No