Approval flow statusCode 429 rate limit is exceeded

Like (0) Share

Report

Posted on 13 Nov 2018 16:16:57 by 980Panama

140

I have run an approval flow this afternoon and received an error on 4 of the approvals with the message

429. The request failed. Response content: 'statusCode:429,message Rate limit is exceeded. Try again in 5 seconds.

Can you please let me know what this message means and how I can correct the approvals involved or re-run them.

All responses (4)

Answers (1)

756454530010 2 on 27 Oct 2021 at 03:36:20

Like (0)

Report

Re: Approval flow statusCode 429 rate limit is exceeded
Community Power Pla... on 05 May 2020 at 11:04:23

Like (0)

Report

Re: Approval flow statusCode 429 rate limit is exceeded

SO I am facing a similar issue for Azure DevOps Connector, it says it ha 60 per 60 seconds as the throttling limit.

So my actual confusion is that is this limit applies to all the connectors of Azure DeVops together used in the flow run?
Since I am having 2 connectors "Create a Work item" and "Get Query resul" so if I make 60 runs in a minute these both will throttle after 30? or they will have their individual limit set to 60.?
980Panama 140 on 14 Nov 2018 at 13:48:39

Like (0)

Report

Re: Approval flow statusCode 429 rate limit is exceeded

Many thanks Mabel it is good to have this explained and the article referenced is very good.
Verified answer

v-yamao-msft on 14 Nov 2018 at 08:58:47

Like (1)

Report

Re: Approval flow statusCode 429 rate limit is exceeded

Hi @980Panama,

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

Error code 429 means that your quota of times you can ping a service in the interval that is predetermined.

I assume that you’ve got a number of approval requests within a given time that exceed the rate limit.

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

Besides, I have seen a blog on the similar issue, please check it for a reference:

https://veenstra.me.uk/2018/07/16/microsoft-flow-error-429-rate-limit-is-exceeded-try-again-in-x-seconds/

Best regards,

Mabel