Forum Discussion
SharePoint 429 Error - Throttling
We have a custom code application which hits SharePoint with multiple ExecuteQueries. This has been running fine for 6 months. From last week, we began receiving a lot of 429 Errors.
We made sure that that there is a delay of up to 3 secs between each ExecuteQuery and also decorated the HTTP calls as Microsoft suggest in (https://docs.microsoft.com/en-us/sharepoint/dev/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online). Also multiple users are being used so that not always the same user is used when hitting SharePoint.
Has anyone encountered this? Does anyone know the actual values of throttling in SharePoint or what triggers it?
HELLO Justin Spiteri. I am not a coder but i use onedrive like online cloud storage. I have been facing this issue since 3 months and i am still unable to get help. PLEASE CAN YOU GUIDE ME TO SOLUTION?? i am unable to access my important files on my online drive!. m4eer9kc9060@onedrive.69ssr.us this is my mail. I WILL BE VERY GRATEFUL FOR YOUR KINDNESS.
In case you haven't seen it, there's new guidance regarding throttling.
The latest version of CSOM (16.1.8316.1200) added support for RetryQuery when throttled.
It will not change anything in relation to when you're being throttled. It changes the way it should be handled.
https://github.com/SharePoint/PnP-Sites-Core/issues/1892
We have encountered again error 429 and also error 503 last week. Although we haven't seen any more in the past 4 days, we are curious again on what might have triggered this issue. We have told our users to not use SharePoint for the time being, so that might have helped in stopping these errors, but we cannot say for sure.
From our end, the only new change we did is that we started evaluating a 3rd party software (Metalogix) to take a backup of our Office 365 solution. Our tests were mainly backing up of 2 small mailboxes (multiple times due to different tests) to our Azure blob storage.
Would it be possible that our solution (previously mentioned) together with Metalogix caused this issue again?
All we would like to know is:
1. How are we being throttled?
2. How could we know what is causing the throttling?
3. What are our limits?
Currently we are in a situation where the company is constantly growing and of course we are constantly increasing the adoption of Office 365 to all our users, especially in SharePoint and Teams. Our fear is that if we increase more usage and applications on our Office 365 solution, the more we are going to encounter these throttling issues. So without having any information on the 3 points mentioned above, we cannot plan any future applications on SharePoint.
Does anyone encountered the same issue lately?
Hi,
Yes this is probably causing the issue. I have been told during Inspire 2018 in Vegas that the main issue with the tenants is caused by the increase of activities using backup software. Microsoft is therefore using algoritmes to block throttle backup software.
Can you try running after working hour backups?
Instead of 3 seconds delay between each query, you can execute one after the other. If you encounter 429 error, just inspect the response header for 'retry-after' entry. This retry-after field will contain the number of seconds you need to wait until you make your next query.
We already have tried this but unfortunately when there is a 429 error, and the ExecuteQuery retries, the returned information will contain missing fields. For example the File name of the item is returned as empty.
So unfortunately this was leading us to other issues and that's why we created a delay of 3 secs between each ExecuteQuery.
ExecuteQuery retries, the returned information will contain missing fields - This should not happen!. Can you share your retry code?
- Thanks Robert,
Very interesting and we'll try it out.
Our main concern though is that we haven't been able to obtain a reply in 3 days if the site has been throttled and why, so as to resolve this and ensure it is not triggered again.
