I have a flow that, yes, calls other flows. Never thought that would be a problem, but trying to run today I get this error message. So, what are the limits? Can we get them expanded? This is like a compiler complaining that we're calling too many subroutines...should be a problem that was solved decades ago.
In their documentation, it states 30 is the max: https://docs.microsoft.com/en-us/power-automate/desktop-flows/how-to/run-desktop-flow-action
Must be a heckuva flow! 🙂
@LogicSmith Please refer this explanations:
Also try to :
split your extensive flows into multiple to split the action count.
click on a flow and go to its analytics to see its usage
Hope it helps!!
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.
Sadly, this produces more questions than answers for me.
So, not sure how this works. For instance, I have a flow called Log, which takes a filename and some text, and writes the text to the file with a timestamp. Every flow I write calls this flow.
I have a flow that tests APIs in our newest product. I expect to have one flow that calls one flow for each API call, but doing this I hit that 30 flow limit. So...can I divide those 30 flow calls into 3 flows that each call 10 other flows? Or will that still put me over the 30 limit if I have one flow that calls three flows that each call 10 more flows? And every flow calls the Log flow? And what happens if I have a cloud flow that then calls a desktop flow that then calls all these other flows?
And of course the final question, what kind of manager decided on a limit of 30? As a developer, I could see a limit of 255, or a limit of 65k, but 30? Seriously?
I could not understand the requirement that is causing to have 30 interdependent flows. Sorry about that.
From the description it looks like you have created a separate Flow that gives a Logging functionality.
This Flow can be called as many times from another Flow.
You can always call the same flow n number of times by passing the right parameters making it reusable.
Hope you are making use of Input/Output parameters. Also think of Subflows wherever possible.
In my defense, I am using PA for an unintended purpose - that of a test automation tool. My plan was to use the "one ring to rule them" approach. I have X number of API tests - some simple, some complex. While I want the ability to run them all individually, I also want one flow that runs them all. I have Y number of UI tests, Z number of console app tests. I think this gives me greatest freedom for expandability, and using smaller flows where possible will make reusability easier as our QA department grows. I had not really considered sub-flows as they're sub to one particular flow, not reusable, but in some cases that may be possible. I can work with this max of 30, but it will change the process somewhat.
Many of my flows, since they are only called from one other flow, have been shuffled off into sub-flows, which helps. But it begs the question...do sub-flows count toward that max of 30? Or do only "external" flows count toward the 30?
Don't know if it is mentioned anywhere in the MSFT documentation. But I have come across a post on this forum where a member had written 53 sub flows without any issues.