Skip to content

Commit 65d32da

Browse files
adambuVesaJuvonen
authored andcommitted
Language is unclear and we are seeing ISV's not following the guidance. (SharePoint#1952)
Updating user-agent recommendations around avoiding throttling with remote API calls in SPO.
1 parent 0782411 commit 65d32da

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/general-development/how-to-avoid-getting-throttled-or-blocked-in-sharepoint-online.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ The most common causes of per-user throttling in SharePoint Online are client-si
7272
A single process dramatically exceeds throttling limits, continually, over a long time period.
7373

7474
- You used web services to build a tool to synchronize user profile properties. The tool updates user profile properties based on information from your line-of-business (LOB) human resources (HR) system. The tool makes calls at too high a frequency.
75-
75+
7676
- You're running a load-testing script on SharePoint Online and you get throttled. Load testing is not allowed on SharePoint Online.
7777

7878
- You customized your team site on SharePoint Online, for example, by adding a status indicator on the Home page. This status indicator updates frequently, which causes the page to make too many calls to the SharePoint Online service - this triggered throttling.
@@ -110,11 +110,11 @@ To ensure and maintain high-availability, some traffic may be throttled. Throttl
110110

111111
What is definition of undecorated traffic?
112112

113-
- Traffic is undecorated if there is no AppID/AppTitle or User Agent string in CSOM or REST API call to SharePoint Online.
113+
- Traffic is undecorated if there is no AppID/AppTitle and User Agent string in CSOM or REST API call to SharePoint Online. The User Agent string should be in a specific format as described below.
114114

115115
What are the recommendation?
116116

117-
- If you have created an application, recommendation is to register and use AppID and AppTitle – This will ensure the best overall experience and best path for any future issue resolution. Include also the User Agent string information as defined in following step.
117+
- If you have created an application, the recommendation is to register and use AppID and AppTitle – This will ensure the best overall experience and best path for any future issue resolution. Include also the User Agent string information as defined in following step.
118118

119119
- Make sure to include User Agent string in your API call to SharePoint with following naming convention
120120

0 commit comments

Comments
 (0)