Skip to content

Commit 66b3182

Browse files
authored
A word
1 parent f4b9a64 commit 66b3182

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ For requests that a user performs directly in the browser, SharePoint Online red
3333
For requests that an application makes, including [Microsoft Graph](/graph), CSOM or REST calls, SharePoint Online returns HTTP status code 429 ("Too many requests") or 503 ("Server Too Busy") and the requests will fail.
3434

3535
- HTTP 429 indicates the calling application sent too many requests in a time window and exceeded a predetermined limit.
36-
- HTTP 503 indicates the service isn't ready to handle the request. The common cause is that the service is experiencing temporary load spikes then expected.
36+
- HTTP 503 indicates the service isn't ready to handle the request. The common cause is that the service is experiencing more temporary load spikes than expected.
3737

3838
In both cases, a `Retry-After` header is included in the response indicating how long the calling application should wait before retrying or making a new request. Throttled requests count towards usage limits, so failure to honor `Retry-After` may result in more throttling.
3939

0 commit comments

Comments
 (0)