Respond to PowerApps Error: 'schema definition for action with status code '200' is invalid. The schema definitions for actions with the same status code is missing.'

[Jeevarajan04]

Was in the middle of designing flow and the error was throw on trying to save the Flow

'schema definition for action with status code '200' is invalid. The schema definitions for actions with the same status code is missing.'

Initially thought it was because of Custom API I had.  To replicate it, I just created this dummy Flow with no external integrations. Just a conditional step with being static values returned to PowerApps by 'Respond to PowerApps' step. 

The moment I add a variable in the Respond to PowerApps in 'If No' step, the error starts popping and doesn't allow me to save further.

Am I doing a silly mistake here? Early help would be much appreciated.

[v-bacao-msft · Accepted solution]

Hi @Jeevarajan04 ,

I did the test on my side, it seems that the same content was added in Title field, so this error occurred.

The default value of Title field is text, which is automatically populated after the Flow is saved.

Please try removing the two Respond to PowerApps actions and reconfiguring the two actions.

It should be noted that this time only the Value field is configured, you do not need to configure the title, and then click Save.

Image reference:

Please take a try again.

Best Regards,

[sarveshshinde15]

Thanks for the suggestion. I tried this solution but in my case it didnt work.

In my FLOW I needed to add "Respond to PowerApps" action multiple times in different conditional branches. So it was failing with same error.

At the end I could come over the problem by saving my response in a variable. Set the variable in different conditional branches multiple times.

And at then end of all actions/branches add "Respond to PowerApps" only once in whole FLOW and use variable in it.

Hope this helps someone.

[Anonymous]

I noticed that by using "Peek code" I could see it was not actually saving my title/values in the Respond to PowerApps action. The schema was basically two empty objects which is why it didn't want to save since the rest of my other responses have their values.

I got around this by adding my titles/values in with the action outside of a conditional, confirming the schema values with "peek code", then dragging and dropping into the yes/no condititon.

[kalyani]

Hi, 

I have the same scenarios like yours, I need to send to one power app if flow got failed or got succeeded, could you please share your flow screenshot how you have handled thank you

[michaelshparber]

@sarveshshinde15  Awesome, Thank you!

[divya-akula]

Similar Issue happened to me when there are multiple Respond to PowerApp or flow actions and their responses aren't matching. Once the actions are matched with same response parameter names , response value types and the count of response parameters, it fixed the issue. Hope it helps someone 

[Anonymous]

I had the same issue. The solution is to make sure all responds has the same output.

[sneff]

Hello, I am having the same issue you had. I need to have a response to virtual agents if my flow fails but keep having errors.

Could you help me or anyone else?

[befa]

I had two 'Respond to PowerApps' actions, and both were empty since I don't need to return any data. I got the same error. From 'Anonymous' user's comment here I realized I could look at the code. There I found that they have different return schemas even though neither returns anything:

"inputs": {
  "schema": {
    "type": "object",
    "properties": {}
  },
  "statusCode": 200
}

"inputs": {
  "schema": {
    "type": "object",
    "properties": {},
    "additionalProperties": {}
  },
  "statusCode": 200,
  "body": {}
}

I remove and added back the action with the extra fields (additionalProperties and body), and I was able to save the flow. Now both actions have the first pattern out of the ones I've shown here, without extra fields.