Failed to Save, Definition contains Invalid Paramters

Like (0) Share

Report

Posted on 2 Jun 2017 18:20:35 by WiggityZwiggity

356

I am receiving a generic error on an very large flow created and run several times that says "Failed to Save, definition contains invalid paramters". There is nothing else in the error message that would indicate what that could be. I can discard edits, re-open, and modify a single thing (delete an action, modify an action) and saving always generates this message.

Any way I can figure out what's going on here?

I have the same question (0)

All responses (7)

Answers (1)

ntubergen-grymc 8 on 10 Aug 2020 at 19:08:28

Like (0)

Report

Re: Failed to Save, Definition contains Invalid Paramters

A fix that worked for me. Initialize (or set) the entire body as the string variable. MS didn't like some text and a variable. See screencap below. Hope this finds its way back to you people.

Was this reply helpful? Yes No
VikasSukhija 4 on 19 Aug 2018 at 22:18:30

Like (0)

Report

Re: Failed to Save, Definition contains Invalid Paramters

My error resolved by upadting the list to set some fields as optional , updating the flow and again setting them as mandatory.
I have documented it with some detail https://syscloudpro.com/2018/08/19/microsoft-flow-definition-contains-invalid-parameters/

Was this reply helpful? Yes No
Yury 7 on 26 Apr 2018 at 14:23:40

Like (1)

Report

Re: Failed to Save, Definition contains Invalid Paramters

Hi!
I had the same error showing off. The problem in my case was that after the initial creation of the flow I made some fields in sharepoint list mandatory. Thus, these fields had to be updated after approval/decline and corresponding parts of the flow had to be adjusted as well. So go through all blocks of your flow an check if there are fields with an asterix sign which are empty.
Hope this will help!

Was this reply helpful? Yes No
WiggityZwiggity 356 on 18 Sep 2017 at 12:41:50

Like (0)

Report

Re: Failed to Save, Definition contains Invalid Paramters

I used a compose action and then used the @string([Field]) expression. I then used the output from that compose action as input to set the string type variable.

Was this reply helpful? Yes No
Community Power Pla... on 15 Sep 2017 at 15:01:36

Like (0)

Report

Re: Failed to Save, Definition contains Invalid Paramters

I know this is an old post but if you can share how you created the WDL I would be most appreciative. I can't seem to find resources for this anywhere and I am getting the same error as you when trying to initialize a variable.

Was this reply helpful? Yes No
Verified answer

WiggityZwiggity 356 on 05 Jun 2017 at 15:10:23

Like (0)

Report

Re: Failed to Save, Definition contains Invalid Paramters

I was setting a variable with string type to a string, and for some reason without writing out the WDL expressing @string() it would not accept the set variable option. That seemed to correct it.

Was this reply helpful? Yes No
v-yamao-msft on 05 Jun 2017 at 06:45:12

Like (0)

Report

Re: Failed to Save, Definition contains Invalid Paramters

Hi WiggityZwiggity,

Could you tell me how large your flow is and how your flow is configured?

Do you mean that after deleting or modifying an action then you will get the error message when saving the flow?

Could you show me a screenshot for a reference?

If possible, please also provide your Flow Id for a further investigation.

Best regards,
Mabel Mao

Was this reply helpful? Yes No