Showing results for 
Search instead for 
Did you mean: 
Not applicable

Getting new 429 Errors on several Flows



This week I've started getting 429 errors on several of my Flows that I previously have had no issue with. Just an example I have a Flow that is triggered when I receive an email in one of my Outlook folders, it gets an item in SP and then updates that item. Pretty simple and straightforward and again, never had any issues. All of a sudden the Flow is failing sometimes and giving the 429 error. Again, this is happening on several of my other Flows as well. Is there a known issue that could be causing this? Please Help! Thank you!

Flow ConfigurationFlow ConfigurationFlow ConfigurationFlow ConfigurationErrorErrorErrorErrorErrorError

Community Champion
Community Champion

Hi @Anonymous,

How often is your flow action triggered?


"Rate limit is exceeded" typically means that you've met your quota of times you can ping a service in the interval that is predetermined. As an example, Google Sheets has a limit of 500 requests per 100 seconds per project, and 100 requests per 100 seconds per user. Or Microsoft translator allows you to use it 150 times/day/user.


So it is likely you reached a quota too soon--you're receiving too much email O_O


Mr. Dang



Microsoft Employee
Community Support
Community Support

Hi @Anonymous,


How many times has your flow been fired during one minute?


I agree with @mr-dang's thought almost, the HTTP 429 error indicates that the user has sent too many requests in a given amount of time ("Rate limit").


If the amount of your flow be triggered in a given time is more than the Rate limit, the 429 error would show up. In other words, if your Outlook mailbox received too many emails with the specific subject (Subject filter) in a given time (more than the Rate limit), the issue would show up.


Please take a try to reduce the amount of the requests sent in a given time to fix your issue. 


Best regards,


Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Not applicable

Thank you @v-xida-msft and @mr-dang. I do have a clarifying follow up. Are the number of requests that can't be exceeded specific to the Flow or the connector? For example I have a different Flow that I am seeing this issue with today. The Flow runs when a SP list item is created and gets items from another SP list. The first list isn't part of any other Flows but the second list is part of several Flows. Could the fact that the second list is being called in other Flows cause 429 errors in this Flow?

Helpful resources

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

New Power Super Users


We are excited to announce the Power Apps Super Users!

Power Apps Community Call

Power Apps Community Call: February

Did you miss the call? Check out the Power Apps Community Call here.

Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

Top Solution Authors
Top Kudoed Authors
Users online (35,160)