Showing results for 
Search instead for 
Did you mean: 

JSON ValidationFailed

I have a HTTP call to a REST API.  The endpoint has a limit parameter e.g.


When I set limit to 250 it run the flow perfectly without any error and create sharepoint list items as required.  However, when I increase the limit to 300 (there are 259 objects in this requests) I get this error.  If JSON Schema is not correct I thought I should get the same error with the limit of 250??  The same request works fine on the Postman and return all the objects i.e. in this case 259.


[ { "message": "Invalid type. Expected String but got Null." } ]



Accepted Solutions

Hi Sameer,


You can look in the failed flow run (expand on the HTTP action card) and see the exact output from your service. Do you see anything missing in there?


View solution in original post

Power Automate
Power Automate

Hi Sameer,



where are you seeing this error? Are you onboaring a new Custom connector and testing?


There's a 250 limit with paging links so at flow execution time, it should work properly.




I am getting this error when parsing the json object/response recieved from HTTP.  I have provided some screenshot to your team through twitter DM.  Are you saying that there is a limit for 250 elements?











I looked at a flow run for the failed case and the service is not returing a JSON object - Can you check? In the headers the content-type is text/html.


Also - the body object is not a well formed JSON object - I see the same errors parsing hte object with JSON editors " Expecting 'STring', got 'undefined.

@RajRa  Thanks.  This can't be correct as I have the same flow running with a limit of 250.  If header of json format is not correct I should get the same error with 250 elements.  Here is the screenshot for flow running successfully with 250 limit.



Hi Sameer,


You can look in the failed flow run (expand on the HTTP action card) and see the exact output from your service. Do you see anything missing in there?


@RajRa  I think I am not explaining it correctly.  Let me try again:


  • If you see the screenshot above the flow is working fine.  The endpoint used is for example  The HTTP request returns 250 data elements which I parse through JSON Parse and create items on the SharePoint list.  No issues here.


  • If I change the end point to  I get the json validation error (provided above and also through twitter dm). There is no issue with the endpoint as I have tested this with Postman and other api explorer and it is working fine as expected. 


  • f there is a problem with my json payload, header or structure (as suggested) provided in my flow, I should get the same error when I am asking 250 items? correct?


Can you please confirm that there is no limit on number of items returned through HTTP or is this a bug? You can check the flow I last ran and you will see it worked fine with 250 items.


Thanks, Sohail




I understand what you are saying - It makes sense that you should not see a difference between 250 vs 300 items.


I looked at the output for your flow and I saw the response for the failing case was set to content-type text/html not JSON - Did you confirm?


All this information is available for you in the run history for your flow - you can see the inputs and outputs to each step. Can you confirm that the output that the service returned is JSON and valid? If you see the optput for the failure case you'll see all the entries in there, I can private IM you the details since this is PII if you want.


There are no 250 limits on our side.






I need more information on this. I debugged a success vs non-success case and I don't see any difference in the ouptuts from your service. Can you please IM me the following


1. A failing run (go to the flow run and paste the URL from the failed run - the picture you posted)

2. A successful flow run 

3. The error you are seeing.




Advocate I
Advocate I

You can modify your JSON from {"Name":"String"} to {"Name":["String","Null"]} so he can accept Null values too.

Wanted to thank you for this solution. very very very helpful. 


Also as an FYI, i had to make sure {"Name":"String"} to {"Name":["String","Null"]}  was {"Name":"String"} to {"Name":["String","null"]}


Hello, you need to confirm whether your JSON has grammatical errors first? Please follow the  specification carefully, if you are not sure, you can use JSON Validator  to check

Helpful resources


Community will be READ ONLY July 16th, 5p PDT -July 22nd

Dear Community Members,   We'd like to let you know of an upcoming change to the community platform: starting July 16th, the platform will transition to a READ ONLY mode until July 22nd.   During this period, members will not be able to Kudo, Comment, or Reply to any posts.   On July 22nd, please be on the lookout for a message sent to the email address registered on your community profile. This email is crucial as it will contain your unique code and link to register for the new platform encompassing all of the communities.   What to Expect in the New Community: A more unified experience where all products, including Power Apps, Power Automate, Copilot Studio, and Power Pages, will be accessible from one community.Community Blogs that you can syndicate and link to for automatic updates. We appreciate your understanding and cooperation during this transition. Stay tuned for the exciting new features and a seamless community experience ahead!

Check Out | 2024 Release Wave 2 Plans for Microsoft Dynamics 365 and Microsoft Power Platform

On July 16, 2024, we published the 2024 release wave 2 plans for Microsoft Dynamics 365 and Microsoft Power Platform. These plans are a compilation of the new capabilities planned to be released between October 2024 to March 2025. This release introduces a wealth of new features designed to enhance customer understanding and improve overall user experience, showcasing our dedication to driving digital transformation for our customers and partners.    The upcoming wave is centered around utilizing advanced AI and Microsoft Copilot technologies to enhance user productivity and streamline operations across diverse business applications. These enhancements include intelligent automation, AI-powered insights, and immersive user experiences that are designed to break down barriers between data, insights, and individuals. Watch a summary of the release highlights.    Discover the latest features that empower organizations to operate more efficiently and adaptively. From AI-driven sales insights and customer service enhancements to predictive analytics in supply chain management and autonomous financial processes, the new capabilities enable businesses to proactively address challenges and capitalize on opportunities.    

Summer of Solutions | Week 3 Results | Win free tickets to the Power Platform Conference

We are excited to announce the Summer of Solutions Challenge!    This challenge is kicking off on Monday, June 17th and will run for (4) weeks.  The challenge is open to all Power Platform (Power Apps, Power Automate, Copilot Studio & Power Pages) community members. We invite you to participate in a quest to provide solutions to as many questions as you can. Answers can be provided in all the communities.    Entry Period: This Challenge will consist of four weekly Entry Periods as follows (each an “Entry Period”)   - 12:00 a.m. PT on June 17, 2024 – 11:59 p.m. PT on June 23, 2024 - 12:00 a.m. PT on June 24, 2024 – 11:59 p.m. PT on June 30, 2024 - 12:00 a.m. PT on July 1, 2024 – 11:59 p.m. PT on July 7, 2024 - 12:00 a.m. PT on July 8, 2024 – 11:59 p.m. PT on July 14, 2024   Entries will be eligible for the Entry Period in which they are received and will not carryover to subsequent weekly entry periods.  You must enter into each weekly Entry Period separately.   How to Enter: We invite you to participate in a quest to provide "Accepted Solutions" to as many questions as you can. Answers can be provided in all the communities. Users must provide a solution which can be an “Accepted Solution” in the Forums in all of the communities and there are no limits to the number of “Accepted Solutions” that a member can provide for entries in this challenge, but each entry must be substantially unique and different.    Winner Selection and Prizes: At the end of each week, we will list the top ten (10) Community users which will consist of: 5 Community Members & 5 Super Users and they will advance to the final drawing. We will post each week in the News & Announcements the top 10 Solution providers.  At the end of the challenge, we will add all of the top 10 weekly names and enter them into a random drawing.  Then we will randomly select ten (10) winners (5 Community Members & 5 Super Users) from among all eligible entrants received across all weekly Entry Periods to receive the prize listed below. If a winner declines, we will draw again at random for the next winner.  A user will only be able to win once overall. If they are drawn multiple times, another user will be drawn at random.  Individuals will be contacted before the announcement with the opportunity to claim or deny the prize.  Once all of the winners have been notified, we will post in the News & Announcements of each community with the list of winners.   Each winner will receive one (1) Pass to the Power Platform Conference in Las Vegas, Sep. 18-20, 2024 ($1800 value). NOTE: Prize is for conference attendance only and any other costs such as airfare, lodging, transportation, and food are the sole responsibility of the winner. Tickets are not transferable to any other party or to next year’s event.   ** PLEASE SEE THE ATTACHED RULES for this CHALLENGE**   Week 1 Results: Congratulations to the Week 1 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge.   Community MembersNumber SolutionsSuper UsersNumber Solutions Deenuji 9 @NathanAlvares24  17 @Anil_g  7 @ManishSolanki  13 @eetuRobo  5 @David_MA  10 @VishnuReddy1997  5 @SpongYe  9JhonatanOB19932 (tie) @Nived_Nambiar  8 @maltie  2 (tie)   @PA-Noob  2 (tie)   @LukeMcG  2 (tie)   @tgut03  2 (tie)       Week 2 Results: Congratulations to the Week 2 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 2: Community MembersSolutionsSuper UsersSolutionsPower Automate  @Deenuji  12@ManishSolanki 19 @Anil_g  10 @NathanAlvares24  17 @VishnuReddy1997  6 @Expiscornovus  10 @Tjan  5 @Nived_Nambiar  10 @eetuRobo  3 @SudeepGhatakNZ 8     Week 3 Results: Congratulations to the Week 3 qualifiers, you are being entered in the random drawing that will take place at the end of the challenge. Week 3:Community MembersSolutionsSuper UsersSolutionsPower Automate Deenuji32ManishSolanki55VishnuReddy199724NathanAlvares2444Anil_g22SudeepGhatakNZ40eetuRobo18Nived_Nambiar28Tjan8David_MA22  

Updates to Transitions in the Power Platform Communities

We're embarking on a journey to enhance your experience by transitioning to a new community platform. Our team has been diligently working to create a fresh community site, leveraging the very Dynamics 365 and Power Platform tools our community advocates for.  We started this journey with transitioning Copilot Studio forums and blogs in June. The move marks the beginning of a new chapter, and we're eager for you to be a part of it. The rest of the Power Platform product sites will be moving over this summer.   Stay tuned for more updates as we get closer to the launch. We can't wait to welcome you to our new community space, designed with you in mind. Let's connect, learn, and grow together.   Here's to new beginnings and endless possibilities!   If you have any questions, observations or concerns throughout this process please go to   To stay up to date on the latest details of this migration and other important Community updates subscribe to our News and Announcements forums: Copilot Studio, Power Apps, Power Automate, Power Pages

Users online (4,691)