SharePoint Online Throttling

%3CLINGO-SUB%20id%3D%22lingo-sub-145381%22%20slang%3D%22en-US%22%3ESharePoint%20Online%20Throttling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-145381%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStarting%20last%20Friday%20we%20started%20to%20receive%20an%20significant%20increased%20amount%20of%20429%20responses%20from%20requests%20made%20with%20CSOM%20from%20our%20SharePoint%20Provider%20Hosted%20Add-in.%20The%20same%20started%20to%20occur%20on%20multiple%20tenants%20at%20the%20same%20time%20and%20is%20now%20a%20problem%20on%20up%20to%2060%20different%20tenants.%20We%20are%20using%20best%20practices%20to%20avoid%20Throttling%20like%20decorating%20request%20with%20a%20User%20Agent%20and%20are%20using%20Office%20Dev%20PnP%20ExecuteQueryRetry%20for%20executing%20all%20requests.%20Before%20Friday%20this%20haven%E2%80%99t%20been%20a%20problem%20on%20any%20tenants.%20No%20changes%20are%20made%20from%20our%20site%20to%20cause%20this.%20Any%20help%20would%20be%20appreciated%20to%20shed%20some%20light%20on%20this%20issue%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%2FHenrik%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-145381%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EPnP%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-162436%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20Throttling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-162436%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Henrik%2C%3C%2FP%3E%0A%3CP%3Ethis%20is%26nbsp%3Bnot%20really%20around%20us%20considering%20if%20this%20is%20an%20issue%2C%20it's%20clearly%20an%20issue%20for%20some%20of%20our%20ISVs%2C%20so%20we%20are%20trying%20to%20get%20the%20details%20and%20contacts%20to%20have%20an%20open%20one-to-one%20discussion%20on%20the%20right%20patters%20to%20move%20forward.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECan%20you%20share%20your%20email%20(for%20example%20private%20message)%20or%20send%20me%20directly%20an%20email%20with%20ISV%20solution%20details%2C%20so%20that%20we%20can%20move%20on%20this%20more%20efficiently.%20Thx.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-162389%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20Throttling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-162389%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Vesa%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20you%20for%20taking%20your%20time%20to%20consider%20this%20issue%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20still%20an%20issue%20for%20us%20and%20for%20other%20ISVs%20as%20well.%20We%20did%20raise%20a%20ticked%20that%20ended%20up%20concluding%20that%20our%20multi-tenant%20add-in%20was%20categorized%20as%20an%20app%20that%20performs%20bulk%20operations.%20It%20has%20now%20been%20classified%20as%20interactive%20traffic%20and%20the%20problem%20decreased%20for%20the%20majority%20of%20our%20customers.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20do%20understand%20the%20need%20for%20throttling.%20But%20before%20this%20issue%20started%20we%20never%20received%20a%20single%20429%20response%20from%20SharePoint.%20Now%2C%20on%20some%20tenants%20we%20receive%20a%20very%20high%20percentage%20429%20responses%20compared%20to%20requests.%20For%20example%20we%20have%20one%20tenant%20where%20we%20in%20a%204%20hours%20timeframe%20had%20260%20request%20to%20SharePoint%20where%2083%20of%20them%20is%20Throttled.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMost%20worrying%20is%20it%20that%20in%20periods%20where%20tenants%20are%20Throttled%20we%20cannot%20rely%20on%20CSOM%20ExecuteQuery%20requests.%20We%20often%20see%20that%20we%20receive%20200%20responses%20even%20that%20the%20request%20has%20not%20loaded%20the%20properties%20requested.%20This%20of%20cause%20making%20it%20very%20difficult%20developing%20business%20critical%20solutions%20on%20SharePoint.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHow%20SharePoint%20online%20uses%20throttling%20is%20not%20very%20clear%20to%20us.%20Our%20application%20is%20rather%20complex%20doing%20light%20weight%20stuff%20against%20SharePoint%20in%20remote%20event%20receivers%20in%20a%20user%20context.%20On%20the%20same%20application%20we%20create%20sites%20on%20request%20in%20web%20jobs%2C%20synchronizing%20list%20and%20security%20to%20the%20sites%20executed%20in%20an%20app%20only%20context.%20It%20seems%20that%20SharePoint%20does%20not%20distinct%20and%20both%20cases%20are%20throttled%20equally.%20The%20last%20one%20we%20can%20handle%20with%20exponentially%20back%20off.%20The%20first%20one%20we%20can%20not%E2%80%A6%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAny%20help%20on%20how%20to%20handle%20this%20is%20very%20much%20appreciated...%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%2FHenrik%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-160719%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20Throttling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-160719%22%20slang%3D%22en-US%22%3E%3CP%3EI%20do%20apology%20for%20a%20long%20delay%20in%20the%20response%2C%20but%20let's%20get%20moving%20with%20this%20one.%20If%20this%20is%20still%20a%20problem%2C%20please%20do%20let%20me%20know%20using%20private%20message%26nbsp%3B(email%20or%20TechCommunity)%20and%20we%20can%20start%20a%20discussion%20on%20the%20specifics.%20I'll%20then%20loop%20in%20the%20actual%26nbsp%3Bowners%20of%20the%20throttling%20capability.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-145444%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Online%20Throttling%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-145444%22%20slang%3D%22en-US%22%3E%3CP%3EAdding%20here%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F369%22%20target%3D%22_blank%22%3E%40Vesa%20Juvonen%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi All,

 

Starting last Friday we started to receive an significant increased amount of 429 responses from requests made with CSOM from our SharePoint Provider Hosted Add-in. The same started to occur on multiple tenants at the same time and is now a problem on up to 60 different tenants. We are using best practices to avoid Throttling like decorating request with a User Agent and are using Office Dev PnP ExecuteQueryRetry for executing all requests. Before Friday this haven’t been a problem on any tenants. No changes are made from our site to cause this. Any help would be appreciated to shed some light on this issue?

 

/Henrik

 

 

4 Replies
Highlighted

Adding here @Vesa Juvonen

Highlighted

I do apology for a long delay in the response, but let's get moving with this one. If this is still a problem, please do let me know using private message (email or TechCommunity) and we can start a discussion on the specifics. I'll then loop in the actual owners of the throttling capability. 

Highlighted

Hi Vesa,

 

Thank you for taking your time to consider this issue

 

This is still an issue for us and for other ISVs as well. We did raise a ticked that ended up concluding that our multi-tenant add-in was categorized as an app that performs bulk operations. It has now been classified as interactive traffic and the problem decreased for the majority of our customers.

 

We do understand the need for throttling. But before this issue started we never received a single 429 response from SharePoint. Now, on some tenants we receive a very high percentage 429 responses compared to requests. For example we have one tenant where we in a 4 hours timeframe had 260 request to SharePoint where 83 of them is Throttled.

 

Most worrying is it that in periods where tenants are Throttled we cannot rely on CSOM ExecuteQuery requests. We often see that we receive 200 responses even that the request has not loaded the properties requested. This of cause making it very difficult developing business critical solutions on SharePoint. 

 

How SharePoint online uses throttling is not very clear to us. Our application is rather complex doing light weight stuff against SharePoint in remote event receivers in a user context. On the same application we create sites on request in web jobs, synchronizing list and security to the sites executed in an app only context. It seems that SharePoint does not distinct and both cases are throttled equally. The last one we can handle with exponentially back off. The first one we can not… 

 

 

Any help on how to handle this is very much appreciated...

 

/Henrik

 

 

 

 

Highlighted

Hi Henrik,

this is not really around us considering if this is an issue, it's clearly an issue for some of our ISVs, so we are trying to get the details and contacts to have an open one-to-one discussion on the right patters to move forward.

 

Can you share your email (for example private message) or send me directly an email with ISV solution details, so that we can move on this more efficiently. Thx.