Unanswered

Schema Validation error: Property "" type mismatch, Expected: "object", Actual: "string".

(1) Share

Report

Posted on by rwittels

510

Hi. I have a custom connector which has been working perfectly for over a month. It has 3 actions in it which get various results from Azure API's and I use them in a Power App.

Suddenly, all 3 actions are getting a 200 response but with blank response body and this schema Validation error:

Property "" type mismatch, Expected: "object", Actual: "string".

We have made no changes in both the Azure API's or custom connector.

The Azure API's are still producing the correct outputs in the correct formats and all my custom connector steps are successfully validated.

Tests from Postman work perfectly so the issue is within the Power Platform environment.

What do I need to look for? Has something changed in the custom connector environment on Power Platform?

Categories:

Connector development

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

Michael E. Gernaey 53,335 Super User 2025 Season 2 on at

Like (1)

Report

Hi

Would need to see the code, see the connector in the app, see what its doing if you just call it via a button (so that you are forced to re-use it, instead of looking at results of existing code).

That or create a new Project, and add a button and that connector and see what you get.

Then use Monitor to see if you get more information. You may just need to Refresh the Connector in the App.

Was this reply helpful? Yes No
Suggested answer

Ammar Zaied 97 on at

Like (0)

Report
The error message Property "" type mismatch, Expected: "object", Actual: "string" indicates that Power Platform is expecting a different response structure from your API than what it is receiving. This can happen if there's a subtle change in the API's response format or a misalignment between the response schema defined in the custom connector and the actual output from the API.

Solution:

Revalidate the response schema in your custom connector. Compare the schema that Power Platform expects with the actual response body from Postman to ensure they are still aligned. Sometimes, small changes or additions to the response format in the Azure API can cause this type of mismatch.

If the API response includes optional fields that aren't always present, ensure the schema handles this by allowing nullable values or optional properties.

Check the Power Platform release notes or any known issues that Microsoft might have published recently to see if others have encountered similar issues.

Was this reply helpful? Yes No