Unable to add flow

[aarnav]

Hi All,

I am getting an error when trying to add a Flow. The error message says 'The flow input and output schema cannot be represented in WADL. code: FlowWadlConversionNotSupported' 

I actually updated an existing flow to allow PowerApps to pass one extra parameter. I got an error when refreshing the existing flow. The error message is 'The flow input and output schema cannot be represented in WADL.
code: FlowWadlConversionNotSupported' .  This is the reason I created a new flow.

The new flow was created by clikin on 'Add new' in the power app maker. It did work initially and srated throwing hte error when I made update to parse JSON. I have removed the JSON parsing part and the error is still there.

Did anyone have similar issue?

Thanks,

[Yuvarani]

Hi @aarnav 

Please check whether you have turned on your flow or not, sometimes it may throw you some errors, or you need to recreate a new flow by avoiding an exception.

Refer to the below link for your reference,

Turn flows on/off 

If you want to go through the entire concept feel free to visit our website here : Dynamics Labs 

[aarnav · Accepted solution]

I changed the trigger from power app to 'PoerApps 2.0', re-created the variables are required to be passed from power apps and saved the flow. 

This has resolved the issue for me.

[micross]

When I tried this solution the option to "ask in powerapps" for defining the variable is no longer available. How did you go about setting up your variables?

[nitesh_adi]

When you remove the trigger and add it back, it will give option to re-initialize the variables. I tried the above steps and it works fine.

[todd-fraser]

I was getting this same issue and I think it just means there is a schema mismatch between what you're feeding your response action and what it's expecting.  Here was my solution.

Check your schema definition in your Response action.  Make sure:

1) All the data types match the results, no strings being forced into integers, etc

2) All key-value pairs HAVE a data type

I built my flow using dummy data, and used that same dummy data to generate my response schema, all worked great.  Then I had to add one or two additional key value pairs to the response.  I used a real query result from my data source to re-generate the schema and thought I was good.  PowerAutomate was happy to save.

The issue was when I added two more keys, I used real query results to generate the schema and my real results had two NULLs in them.  The schema left those data types out, because it didn't know how to interpret them.  Once I added "type": "string" for each of them, my issues went away.

I tried replacing the trigger, using PowerApps v2 and all kind of things.  I just missed something on my schema.

[Mach_GO_GO_GO]

Thank-you so much. Wish I would've come across this answer an hour ago.

[lindanicla]

same happens to me

[Mach_GO_GO_GO]

If you want to send me your schema to take a look at, I'll see if I can find anything. 

[mkredpoint]

this saved me! thank you!!