A while back I created a post about limits in Microsoft Teams. Today I’m looking at limits within Microsoft Flow.

Number of Flows created by a user

When you are happily creating many flows and you think that there is no limit to what you can do with Microsoft Flow then you might run into this one! There is a limit of 250 flows that a single user can create. After this you simply get the following error and you can’t save any more flows.

If you hit the 250 limit you can raise a support ticket and then the limit will be raised.

Microsoft Flow - This is the limit! Microsoft Flow, Microsoft Office 365 numberofflows

Do Until limited to 60 runs by default

When running Do Until loops Flow will only run 60 times through the actions inside a Do until.  Luckily it is possible to change this limit within the flow editor.

Microsoft Flow - This is the limit! Microsoft Flow, Microsoft Office 365 dountil60

The above limits I didn’t find on any of the Microsoft Limitation pages.

If you are interested in other limitation  here is the official Limits and configuration in Microsoft Flow post.

Some of the interesting limits from the above article I’ve included below.

Run duration and retention

These are the limits for a single flow run.

Run duration30 daysIncludes workflows with pending steps like approvals. After 30 days, any pending steps time-out. Timed-out approvals are removed from the approvals center. If someone attemps to approve a timed-out request, they’ll receive an error message.
Storage retention30 daysThis is from the run start time.
Min recurrence interval1 minute
Max recurrence interval500 days

Looping and debatching limits

These are limits for a single flow run.

ForEach items5,000You can use the filter action to filter larger arrays as needed.
Until iterations5,000
SplitOn items5,000
ForEach Parallelism1

Definition limits

These are limits for a single flow.

Actions per workflow250You can add nested workflows to extend this as needed.
Allowed action nesting depth5You can add nested workflows to extend this as needed.
Max characters per expression8,192
action/trigger name limit80
description length limit256

What should we do with these Microsoft Flow Limitations?

When looking at the Definition limits. I’m slightly worried about the Actions per workflow and the Allowed action nesting depth most of the other limits you can easily work around. but these two limits mean that when your flow has grown to much you will be stuck and are forced to split your flow across multiple flows. This is where it becomes important to design your flows the right way straight from the beginning. Even when your flow is still quite small.

Avatar for Pieter Veenstra

By Pieter Veenstra

Business Applications Microsoft MVP working as a Principal Architect at HybrIT Services Ltd. You can contact me using contact@sharepains.com

7 thoughts on “Microsoft Flow – This is the limit!”
  1. […] Depending on your use case, you might not be able to re-create your timer job in Flow.  Because you can’t write Full Trust Code in SharePoint Online, you are limited to the actions that you can do through the SharePoint REST API.  Additionally, there are some limitations with Flow specifically such as a single user cannot create more than 250 individual Flows.  Pieter Veenstra has a great blog post that highlights some of the limits within Flow which you can find here: https://veenstra.me.uk/2018/04/30/microsoft-flow-this-is-the-limit/ […]

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Discover more from SharePains by Microsoft MVP Pieter Veenstra

Subscribe now to keep reading and get access to the full archive.

Continue Reading

%d bloggers like this: