Forum Discussion
SharePoint 429 Error - Throttling
I guess you might be having a lot of calls to ExecuteQuery, I suggest you to try to reduce the calls by loading it them in single context and fire as a single call.
We just got hit with this today as well. In my case i simply connected via powershell to enable a cdn and got a 429 back from a single request. I've seen a few posts on this. feels like something changed recently
- We had the same. After converting motlre than 6Tb without any problems using sharegate we were throttled migrating a small delta. Microsoft told us that we were throttled only during business hours. When converting in the weekends and after business hours we did not get the 439 errors anymore!!! Maybe you should try this as well! Good luck!
At least you got that reply :)
We have been in contact with Microsoft Support for quiet a while now and we did not get any specific reply like yours :/
However it does not make sense that you are being throttled during business hours for normal use. We have been using this scenario for months (after multiple migrations to SharePoint) and we never had this issue. So I find it very strange that all of a sudden we began to experience this throttling issue.
One item which Microsoft told us was that it could be the case that other tenants could be effecting the overall SharePoint experience, hence effecting other tenants. But again it does not make from a customer perspective.
I've been battling this for a few weeks now as well and have a support ticket open with Microsoft. Decorating the requests with a UserAgent has helped as per this guidance
It seems you can make up and Company name | Product Name | Version and although the article say to "register" the app, I've not been able to find anyone in Microsoft which whom to give these values to. It seems the mere presence of the values in the right format makes a difference but won't prevent the 429 responses from occurring. Our testing has concluded that the 429 throttling responses (without decorating the requests) happens during business hours at the data centre (peak times) and is heavily influences by other traffic happening in the data centre at the time and not purely how many and how frequent the calls from your code is. e.g. I can get a 429 making a single call (no other calls for hours before it), yet I can make > 5000 calls to SharePoint in a couple of minutes and not get a single throttling error.
As an aside I've identified an issue using the Graph API to access SharePoint items where it will always return a 429 throttling response when it's actually the query hitting a SharePoint threshold (large list) limit so you will want to check this isn't the case if you are seeing this issue as that one is easier to identify and avoid!
