Skip to content

Commit 6e58473

Browse files
Merge pull request #258764 from KrishnaG-MSFT/patch-354
(AzureCXP) MicrosoftDocs/azure-docs#117129
2 parents 60ed7dc + 240fac9 commit 6e58473

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

articles/azure-resource-manager/management/async-operations.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,9 @@ If `Azure-AsyncOperation` isn't one of the header values, then look for:
4242
> [!NOTE]
4343
> Your REST client must accept a minimum URL size of 4 KB for `Azure-AsyncOperation` and `Location`.
4444
45+
> [!NOTE]
46+
> When the `Retry-after` header is not returned, implement your own retry logic by following the Azure guidelines in [this](https://learn.microsoft.com/azure/architecture/best-practices/retry-service-specific#general-rest-and-retry-guidelines) document.
47+
4548
## Azure-AsyncOperation request and response
4649

4750
If you have a URL from the `Azure-AsyncOperation` header value, send a GET request to that URL. Use the value from `Retry-After` to schedule how often to check the status. You'll get a response object that indicates the status of the operation. A different response is returned when checking the status of the operation with the `Location` URL. For more information about the response from a location URL, see [Create storage account (202 with Location and Retry-After)](#create-storage-account-202-with-location-and-retry-after).

0 commit comments

Comments
 (0)