Error 429

(1) Share

Report

Posted on by AZ-27061240-0

Hi all.

I am getting the error 429 hitting the rate limit of my flow:

"message": "Rate limit is exceeded. Try again in 39 seconds. Please see https://docs.microsoft.com/azure/logic-apps/handle-throttling-problems-429-errors for more details."

Most existing solutions suggest to adjust the concurrency of the connector however, I cannot see the option to adjust concurrency in the new power automate.

Could anyone help with this?

Thanks.

Categories:

Building flows

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

mattavdven 125 on at

Like (1)

Report
Copy link

Link copied!

Hi @AZ-27061240-0,

If you are using a trigger like When a new email arrives you can set the spilt on and concurrency of the trigger.
In the new Power Automate editor by default there is no limit on the amount of parallel runs. Make sure to turn on the Concurrency Limit and set the Degree of parallelism to the desired value. When set to 1 the flows will run sequential and the higher the number, the more flows will run a the same time.

https://learn.microsoft.com/en-us/power-automate/guidance/coding-guidelines/implement-parallel-execution

Set the Degree of parallelism to a value so it does not exceed the limit and throws an 429 error.

Good luck!

3 people found this reply helpful.

Was this reply helpful? Yes No
AZ-27061240-0 10 on at

Like (0)

Report
Copy link

Link copied!

@mattavdven Thank you for your response!

It seems the concurrency control is in the 'for each' action and not the specific connector that is flagging the 429 error.

I will amend the concurrency, check if this fixes my issues and mark as solved if this works.

Thanks!

Was this reply helpful? Yes No
mattavdven 125 on at

Like (1)

Report
Copy link

Link copied!

Hi @AZ-27061240-0,

Then I suggest to change the concurrency within the Apply to each action. This can be done by selecting the Apply to each action and open the settings. As described in my other comment.

If the rate limit after changing the concurrency still exceeds, you can add a Delay action inside the Apply to each i.e. 5 seconds. This will result in an longer duration of each item inside the Apply to each!

2 people found this reply helpful.

Was this reply helpful? Yes No
AZ-27061240-0 10 on at

Like (0)

Report
Copy link

Link copied!

@mattavdven Amending the parallelism on the for each action seems to have solved the issue.

I will call it fixed, if it does throw up the error later, I will re-open the request.

thanks so much for the help!

Was this reply helpful? Yes No