You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-resource-manager/resource-manager-async-operations.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,21 +4,19 @@ description: Describes how to track asynchronous operations in Azure.
4
4
services: azure-resource-manager
5
5
documentationcenter: na
6
6
author: tfitzmac
7
-
manager: timlt
8
-
editor: tysonn
9
7
10
8
ms.assetid:
11
9
ms.service: azure-resource-manager
12
10
ms.devlang: na
13
11
ms.topic: conceptual
14
12
ms.tgt_pltfrm: na
15
13
ms.workload: na
16
-
ms.date: 01/11/2017
14
+
ms.date: 08/21/2018
17
15
ms.author: tomfitz
18
16
19
17
---
20
18
# Track asynchronous Azure operations
21
-
Some Azure REST operations run asynchronously because the operation cannot be completed quickly. This topic describes how to track the status of asynchronous operations through values returned in the response.
19
+
Some Azure REST operations run asynchronously because the operation can't be completed quickly. This article describes how to track the status of asynchronous operations through values returned in the response.
22
20
23
21
## Status codes for asynchronous operations
24
22
An asynchronous operation initially returns an HTTP status code of either:
@@ -31,13 +29,13 @@ When the operation successfully completes, it returns either:
31
29
* 200 (OK)
32
30
* 204 (No Content)
33
31
34
-
Refer to the [REST API documentation](/rest/api/) to see the responses for the operation you are executing.
32
+
Refer to the [REST API documentation](/rest/api/) to see the responses for the operation you're executing.
35
33
36
34
## Monitor status of operation
37
35
The asynchronous REST operations return header values, which you use to determine the status of the operation. There are potentially three header values to examine:
38
36
39
37
*`Azure-AsyncOperation` - URL for checking the ongoing status of the operation. If your operation returns this value, always use it (instead of Location) to track the status of the operation.
40
-
*`Location` - URL for determining when an operation has completed. Use this value only when Azure-AsyncOperation is not returned.
38
+
*`Location` - URL for determining when an operation has completed. Use this value only when Azure-AsyncOperation isn't returned.
41
39
*`Retry-After` - The number of seconds to wait before checking the status of the asynchronous operation.
42
40
43
41
However, not every asynchronous operation returns all these values. For example, you may need to evaluate the Azure-AsyncOperation header value for one operation, and the Location header value for another operation.
0 commit comments