Forum Discussion
SharePoint 429 Error - Throttling
Hi,
we're currently experiencing the same situation in our tenants and our customer's tenants. Since 2/3 weeks ago, the 429 errors are suddenly increasing without any configuration changes or updates.
Also using incremental backoff retry and User Agent.
We created an ASPX page that can be uploaded to any Azure web app and simply performs a CSOM query every 5 sec. against SharePoint online. We can see how this operation returns 429 a significant amount of times in these tenants. In case it's useful for someone, it's attached to this comment.
As we didn't get any official reply from MS yet, did you guys manage to get an explanation or a satisfactory resolution to your cases? Did the errors just go or were there any actions involved?
We feel we're quite in the dark here...
Thank you,
Enric
Please share us details around your issue at https://github.com/SharePoint/sp-dev-docs/issues, so that we can route this properly internally thx.
- Justin SpiteriApr 24, 2018Copper Contributor
Enric Carrión One suggestion I could mention is how we have tried to deal with this situation while these errors were occurring. As mentioned in my previous reply, we modified our solution to stop hitting SharePoint for the amount of time that is mentioned in the 429 error (usually 2 minutes).
Of course this effected us very negatively as all systems were very very slow and we were asking our users to not use the system unless they really need to. But at least we managed to limp trough this situation until somehow it got resolved on it's own.
- Enric CarriónApr 24, 2018Brass Contributor
Hi Vesa,
we already posted https://github.com/SharePoint/sp-dev-docs/issues/1710 and https://github.com/SharePoint/sp-dev-docs/issues/1711 four days ago, and we're collecting data for a third one today.
In the meantime, support tickets are open by these customers, although we didn't get specific replies yet.
So, as some productive systems are affected (= unusable) and every day counts, this is extremely concerning for us, and I wanted to get some feedback from the users that originally faced this 2 months ago.
I understand that every issue needs to be properly diagnosed and assessed, so I really appreciate all the efforts you're already making. Please let us know if we can help with any action/test/troubleshooting from our side. There is critical business around this issue and we're willing to help as much as possible.
Thank you!
Justin Spiteri Thanks a lot for your feedback, I'm glad your issues got solved.