Showing results for 
Search instead for 
Did you mean: 

How to bypass PowerApps V2 Trigger limit of 19 pieces



I am trying to create a button, that would take selected values in Sharepoint List A, and create an item in Sharepoint List B.

The V2 Trigger was working well, until I hit the 19 piece limit.


I'm trying to find a work around that would allow me to move approx. 38 pieces, I read something about using Concatenate & Split, but I'm not familiar. Does that sound right to anyone else?


Any input or ideas are welcome, trying to cast a wide net.


thank you.


To answer your main question: there are a couple of ways around the limit, though you do need a premium account for the simplest methods, you could create a new flow which uses the "request" trigger, this allows you to call this flow from within another and pass data to it, this other flow could then continue to process the data and pass the results back. 


The real issue though is why you're hitting the limit on what sounds to be a simple task. 

Could you give a little more info with regards to what you're trying to accomplish and/or your current flow? 

@RPGpro could you elaborate on the 'couple of ways' i'm trying to find the simplest way around this limit but cant seem to figure it out. i need to populate a word doc with way more inputs. 

You could create a second flow using the "request" trigger type, you can then call this flow from your main one, (essentially creating a sub-process) pass data to that to the sub-flow for processing and then pass back the result. 

This would pass some of your usage over to another flow with its own separate limits. 

Another alternative is to push the data to some other external source through some connector, power apps is a good example as it integrates closely with power automate, but you could also pass the data to a custom JavaScript connector or something else, process the data over there and return the result. 


As an extension of that last point, the external source could be the power apps desktop app, which could then complete the entire process without having to send data back to the web flow (you would need the desktop version of word and oneDrive)


As a really bad but simple alternative, you could ensure that you never hit the API limits by adding a pause into your flow. 

check the API limits for the connector you're having issue with, there should be some amount of regen, for example it might gain 5 calls per 10 seconds. 

Add a "wait" action to your flow to ensure it doesn't go over this limit, given the above example you would need to add a 2 second wait after each action that uses that connector. 

This will of course slow down the flow by a massive amount, but it's an easy solution if you're not bothered about execution time. 



If you're adding data to word, make sure you compile all the data within the flow and then add it to word in a single action, rather than doing small edits with each individual data part. 

For example, if you're processing business card info with 3 inputs: name; job; phone:


Don't do:

read the name -> save to word -> read the job -> save to word -> read the phone -> save to word -> next card -> repeat till no cards left. 


Instead do:

read the name -> save to a variable -> read the job -> append to the same variable -> read the phone -> append to the same variable -> next card -> repeat till no cards left-> save the variable to word. 


Any external connections (including the connection to office365 word) tend to be where you hit API limits and are also the parts that slow down your flows. 


thanks for the input! for the first option, do you mean the http request?

@bloempotje wrote:

do you mean the http request?

Yes, from what I've seen on here it seems to be the most commonly used method for triggering one flow from another. 

thanks for the quick reply, at this moment ive used the parse json method which seems to work but......
do you know anything about a 'set' function and '.run' function in the same 'onselect' button?

Kenteken: TextInput_1.Text;
TypeAfspraak: Combobox_2.Selected.Value;
Merk: Textinput_3.Text;
Klantnaam: TextInput_4.Text;
CSM: ComboBox_5.Selected.Value;
AangemaaktDoor: TextInput_6.Text;
Partij: Combobox_7.Selected.Value;
Model: TextInput_8.Text;
Hardware: ComboBox_9.Selected.Value;
UitvoerDatum: Date_10.SelectedDate;
VerkoopOrdernr: TextInput_11.Text;
NieuwIMEI: TextInput_12.Text;
OudIMEI: TextInput_13.Text;
JC1: jc1.Text;
JC2: jc2.Text;
NC1: nc1.Text;
NC2: nc2.Text

I just noticed that this question was originally regarding limits to number of blocks, not number of calls (hence several of my suggestions mentioning API limits), oops. 

The simplest way around this limit would be to have powerApps compile all the data into a single JSON (or plain text CSV if you don't like JSON) object and pass that as a single argument to the power automate flow, which appears to be the solution you came up with. 


I'm not particularly well-versed with the language powerApps uses, but... in theory it just executes the code sequentially no matter whether it's in an "onSelect" function or elsewhere, it looks like you're maybe missing a closing bracket after the JSON data? (the run function is inside the set function) 


Otherwise it might be best to open a new thread for that question. 

@RPGpro thanks for the help!

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,442)