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/logic-apps/logic-apps-exception-handling.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,7 @@ specify a retry policy, the action uses the default policy.
84
84
85
85
| Value | Type | Description |
86
86
|-------|------|-------------|
87
-
| <*retry-policy-type*> | String | The retry policy type you want to use: "default", "none", "fixed", or "exponential"|
87
+
| <*retry-policy-type*> | String | The retry policy type you want to use: `default`, `none`, `fixed`, or `exponential`|
88
88
| <*retry-interval*> | String | The retry interval where the value must use [ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_representations). The default minimum interval is `PT5S` and the maximum interval is `PT1D`. When you use the exponential interval policy, you can specify different minimum and maximum values. |
89
89
| <*retry-attempts*> | Integer | The number of retry attempts, which must be between 1 and 90 |
90
90
||||
@@ -277,9 +277,9 @@ For limits on scopes, see [Limits and config](../logic-apps/logic-apps-limits-an
277
277
Although catching failures from a scope is useful,
278
278
you might also want context to help you understand
279
279
exactly which actions failed plus any errors or status codes that were returned.
280
-
The "@result()" expression provides context about the result of all actions in a scope.
280
+
The `@result()` expression provides context about the result of all actions in a scope.
281
281
282
-
The "@result()" expression accepts a single parameter (the scope's name)
282
+
The `@result()` expression accepts a single parameter (the scope's name)
283
283
and returns an array of all the action results from within that scope.
284
284
These action objects include the same attributes as the **@actions()** object,
285
285
such as the action's start time, end time, status, inputs, correlation IDs, and outputs.
@@ -338,9 +338,9 @@ for any actions that failed within the scope "My_Scope":
338
338
Here's a detailed walkthrough that describes what happens in this example:
339
339
340
340
1. To get the result from all actions inside "My_Scope",
341
-
the **Filter Array** action uses this filter expression: "@result('My_Scope')"
341
+
the **Filter Array** action uses this filter expression: `@result('My_Scope')`
342
342
343
-
2. The condition for **Filter Array** is any "@result()"
343
+
2. The condition for **Filter Array** is any `@result()`
344
344
item that has a status equal to **Failed**.
345
345
This condition filters the array that has all the action
346
346
results from "My_Scope" down to an array with only the failed action results.
@@ -354,18 +354,18 @@ action result that was previously filtered.
354
354
Multiple failed actions cause one action per failure.
355
355
356
356
4. Send an HTTP POST on the **For each** item response body,
357
-
which is the "@item()['outputs']['body']" expression.
357
+
which is the `@item()['outputs']['body']` expression.
358
358
359
-
The "@result()" item shape is the same as the
360
-
"@actions()" shape and can be parsed the same way.
359
+
The `@result()` item shape is the same as the
360
+
`@actions()` shape and can be parsed the same way.
361
361
362
-
5. Include two custom headers with the failed action name ("@item()['name']")
363
-
and the failed run client tracking ID ("@item()['clientTrackingId']").
362
+
5. Include two custom headers with the failed action name (`@item()['name']`)
363
+
and the failed run client tracking ID (`@item()['clientTrackingId']`).
364
364
365
-
For reference, here's an example of a single "@result()" item,
365
+
For reference, here's an example of a single `@result()` item,
366
366
showing the **name**, **body**, and **clientTrackingId**
367
367
properties that are parsed in the previous example.
368
-
Outside a **For each** action, "@result()" returns an array of these objects.
368
+
Outside a **For each** action, `@result()` returns an array of these objects.
369
369
370
370
```json
371
371
{
@@ -425,4 +425,4 @@ information to other data sources, such as queues, topics, SQL, Azure Cosmos DB,
425
425
*[Find more Logic Apps examples and scenarios](../logic-apps/logic-apps-examples-and-scenarios.md)
0 commit comments