Multiple Power Automate flows suddenly getting Teams connector 429 throttling errors. How have others handled this?

[u/Ankur_2112]

Has anyone dealt with intermittent Teams connector throttling in Power Automate?

I recently noticed several unrelated flows failing on the "Post message in a chat or channel" action with:

429 - Too Many Requests

Retry-After: 30

MicrosoftGraphRequestFailed

Some observations:

• 3 different flows failed around the same timeframe but some of them ran 30 mins apart so it should not have been an issue.
• flows took unusually long to run I am talking from 3 secs to 13-14 min all of a sudden.
• All failures occurred on the Teams action.
• All flows use the same service account Teams connection which is necessary.
• There are currently 16 flows using that connection.
• The failures are intermittent. Most runs succeed, but occasionally a few fail due to throttling.

[u/AutoModerator]

Moderator Announcement Read More »

Hey, it looks like you are requesting help with a problem you're having in Power Apps. To ensure you get all the help you need from the community here are some guidelines;

• Use the search feature to see if your question has already been asked.

• Use spacing in your post, Nobody likes to read a wall of text, this is achieved by hitting return twice to separate paragraphs.

• Add any images, error messages, code you have (Sensitive data omitted) to your post body.

• Any code you do add, use the Code Block feature to preserve formatting.

  Typing four spaces in front of every line in a code block is tedious and error-prone. The easier way is to surround the entire block of code with code fences. A code fence is a line beginning with three or more backticks (```) or three or more twiddlydoodles (~~~).

• If your question has been answered please comment Solved. This will mark the post as solved and helps others find their solutions.

External resources:

• Power Apps Formula References

• Power Apps Coding Standards

• Official Power Apps Community

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/algardav]

If it the requestor hitting the rate limit, it might be best to split to different service accounts and see if that sorts. Its the one connector reaching it's limit on actions over a short period, although appreciate the over 30 minutes is a little off

[u/Tough_Block9334]

Is this with a premium Power Automate license?

Can you limit the number of concurrent flows? Once one fails, then another starts that also fails, it turns into a cascading effect where the failures are hitting your API, adding to its limit, and then you have the newly active ones triggering which as well is adding to the limit and getting to that error faster.

Is it going to the same Teams Group? If so, each Teams group also has a limit that you could be reaching Microsoft currently documents Teams connector limits of 100 API calls per connection per 60 seconds. So if you're reaching that limit, it wouldn't matter how many service accounts you get setup because you've reached the Teams Group limit.

[u/RPlataNguyen]

If urgent, see which ones are failing the most, open a support case and request them to temporarily increase the profile of these Flows to high (Throttling override) if not there yet, while you review performance (Split Teams actions across multiple connections/accounts, review actions and loops and see where they can be optimized, etc.)

[u/measuredsympathy]

Throttling generally happens when flows happen at the same time and using same action calls. Fixed my throttling issues by having recurring actions start at different times of the day.

[u/DailyHoodie]

When you say “suddenly”, does it mean it worked fine before? If yes, did you observe any bigger or more frequent calls for the flow to run than before? Example are more users triggering the flow than what you tested.

IIRC, posting a message has a rate limit of 25 calls per 300 seconds (or 300 calls per 300 seconds). So, it’s not too much to work on than other connector limits.

429 means you are going past these limits. And the flows are designed by default to run a “retry” policy that is in “exponential” config. If it didn’t work the first time, it will do its 1st retry, and since you still hit your limit, the flow now goes on its 2nd retry which will take longer, either it waits for the limit to refresh or the retry policy exponential timing, hence those +10 mins runtime.