Skip to content

Commit 8612a7d

Browse files
committed
new topic
1 parent 3adb03d commit 8612a7d

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/batch/batch-retry-after-errors.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -24,16 +24,16 @@ It is important to remember to check for errors when working with a REST service
2424

2525
## Common errors
2626

27-
- Networking failures which means the request never reached Batch or the Batch response didn't reach the client in time.
28-
- Internal server errors which is a standard 5xx status code HTTP response.
29-
- Throttling can cause errors such as 429 or 503 status code HTTP responses with the Retry-after header.
30-
- 4xx errors which include such errors as AlreadyExists and InvalidOperation. This means that the resource is not in the correct state for the state transition requested by the customer.
27+
- Networking failures - these are requests that never reached Batch or the Batch response didn't reach the client in time.
28+
- Internal server errors - these are standard 5xx status code HTTP response.
29+
- Throttling can cause errors such as 429 or 503 status code HTTP responses with the Retry-after header.
30+
- 4xx errors that include such errors as AlreadyExists and InvalidOperation. This means that the resource is not in the correct state for the state transition.
3131

3232
## When to retry
3333

34-
The Batch APIs will notify you if there is a failure. They can all be retried and include a global retry handler for that purpose. It is best to use this built-in mechanism.
34+
The Batch APIs will notify you if there is a failure. They can all be retried, and they all include a global retry handler for that purpose. It is best to use this built-in mechanism.
3535

36-
After a failure, you should wait a bit (several seconds between retries) before retrying. If you retry too frequently or too quickly, you will be throttled. This is managed by the retry handler.
36+
After a failure, you should wait a bit (several seconds between retries) before retrying. If you retry too frequently or too quickly, the retry handler will throttle.
3737

3838

3939
For detailed information about each API and their default retry policies, read [Batch Status and Error Codes](https://docs.microsoft.com/rest/api/batchservice/batch-status-and-error-codes).

0 commit comments

Comments
 (0)