# Github rule deployment triggers rate limit

**URL:** <https://community.auth0.com/t/github-rule-deployment-triggers-rate-limit/8305>\
**Category:** Get Help\
**Tags:** github, rate-limit, rules, rules-deployment\
**Created:** [September 26, 2017, 7:42pm UTC](https://community.auth0.com/t/github-rule-deployment-triggers-rate-limit/8305 "2017-09-26T19:42:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![walter](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/walter/32/6393_2.png) [@walter](https://community.auth0.com/u/walter)\
**Post date:** [September 26, 2017, 7:42pm UTC](https://community.auth0.com/t/github-rule-deployment-triggers-rate-limit/8305/1 "2017-09-26T19:42:42Z")

</div>

I added one additional rule to my existing rule set and then attempted to deploy the change via GitHub integration. Now, it fails due to what appears to be a rate limit.

Perhaps the github rule deployment should be exempt from the rate limits, no?

## Error

{“statusCode”:429,“error”:“Too Many Requests”}

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [September 26, 2017, 11:06pm UTC](https://community.auth0.com/t/github-rule-deployment-triggers-rate-limit/8305/2 "2017-09-26T23:06:04Z")

</div>

There was a recent change in the limits applied to the Management API for certain tenants so the reason the error surfaced now could be related to that. Having said that there was already limits in place that depending on deployment artifacts count could also be reached so it could be argued that the extension should be considering this and possibly retrying. I’ll relay this internally to the extension team and will get back to you when I have additional information.

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [October 18, 2017, 5:33pm UTC](https://community.auth0.com/t/github-rule-deployment-triggers-rate-limit/8305/3 "2017-10-18T17:33:12Z")

</div>

This situation can now be tracked through this GH [issue](https://github.com/auth0-extensions/auth0-source-control-extension-tools/issues/22), however, the update on the deployment extension may be dependent on an update to another library that is consumed as dependency so it’s slightly more complex than initially anticipated.

* * *

**Update:** the GitHub extension had a version update to include an additional feature and at the same time it included a retry if an error is due to rate limits so you may want to consider updating to latest.

---

<div class="post-metadata">

**Author:** ![jmangelo](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jmangelo/32/7923_2.png) [@jmangelo](https://community.auth0.com/u/jmangelo)\
**Post date:** [November 14, 2017, 10:15pm UTC](https://community.auth0.com/t/github-rule-deployment-triggers-rate-limit/8305/4 "2017-11-14T22:15:52Z")

</div>

@walter provided an update to my answer as the GH extension latest version now includes some retry logic.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [March 2, 2018, 5:56am UTC](https://community.auth0.com/t/github-rule-deployment-triggers-rate-limit/8305/5 "2018-03-02T05:56:41Z")

</div>


