Skip to content

Commit 3ef39b9

Browse files
fixing retryafter
1 parent c4d0781 commit 3ef39b9

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
@@ -201,7 +201,7 @@ Below are some examples to help you understand the `RateLimit` headers:
201201
RateLimit-Reset: 5
202202
```
203203
204-
- An application has consumed 100% of its resource unit quota, so it gets throttled due to this policy. The request is throttled and the `RateLimit` headers are returned. The `Retry-After` matches the `RateLimit-Reset`.
204+
- An application has consumed 100% of its resource unit quota, so it gets throttled due to this policy. The request is throttled and the `RateLimit` headers are returned. The `Retry-After` matches the `RateLimit-Reset`. There are instances, where the retryAfter returns a smaller value. In such cases, the general rule of thumb is to honor the greater of the two values.
205205
206206
```
207207
HTTP/1.1 429 Too Many Requests

0 commit comments

Comments
 (0)