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/error-exception-handling.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -201,28 +201,28 @@ For example, to run the Office 365 Outlook **Send an email** action after the Ex
201
201
202
202
The **Run After** section in the **Settings** pane shows the predecessor action for the currently selected action.
203
203
204
-

204
+
:::image type="content" source="media/error-exception-handling/configure-run-after.png" alt-text="Screenshot shows workflow designer and current action details pane with selected Settings tab.":::
205
205
206
206
207
207
1. Expand the predecessor action to view all the possible predecessor statuses.
208
208
209
209
By default, the "run after" status is set to **Is successful**. So, the predecessor action must successfully finish before the currently selected action can run.
210
210
211
-

211
+
:::image type="content" source="media/error-exception-handling/change-run-after-status.png" alt-text="Screenshot shows current action and its default run after status set to Is successful.":::
212
212
213
213
1. To change the "run after" behavior to the statuses that you want, select those statuses. Make sure that you first select an option before you clear the default option. You have to always have at least one option selected.
214
214
215
215
The following example selects **Has failed**.
216
216
217
-

217
+
:::image type="content" source="media/error-exception-handling/failed-run-after-status.png" alt-text="Screenshot shows current action with run after behavior set to Has failed.":::
218
218
219
219
1. To specify that the current action runs when the predecessor action completes with **Failed**, **Skipped**, or **TimedOut** status, select these statuses.
220
220
221
-

221
+
:::image type="content" source="media/error-exception-handling/run-after-multiple-statuses.png" alt-text="Screenshot shows current action and multiple selected run after statuses.":::
222
222
223
223
1. To require that more than one predecessor action runs, each with their own "run after" statuses, expand the **Select actions** list. Select the predecessor actions that you want, and specify their required "run after" statuses.
224
224
225
-

225
+
:::image type="content" source="media/error-exception-handling/multiple-predecessor-actions.png" alt-text="Screenshot shows current action and available multiple predecessor actions.":::
226
226
227
227
1. When you're ready, select **Done**.
228
228
@@ -309,7 +309,7 @@ For limits on scopes, see [Limits and config](logic-apps-limits-and-config.md).
309
309
310
310
1. In the **Scope** action, [follow these generic steps to the add actions to run](/azure/logic-apps/logic-apps-control-flow-run-steps-group-scopes#add-steps-to-scope), for example:
311
311
312
-

312
+
:::image type="content" source="media/error-exception-handling/add-actions-into-scope.png" alt-text="Screenshot shows workflow designer with actions grouped inside the scope.":::
313
313
314
314
The following list shows some example actions that you might include inside a **Scope** action:
315
315
@@ -329,7 +329,7 @@ For limits on scopes, see [Limits and config](logic-apps-limits-and-config.md).
329
329
330
330
In the following example, the scoped actions run after the **HTTP** action completes with any of the selected statuses:
331
331
332
-

332
+
:::image type="content" source="media/error-exception-handling/set-run-after-in-scope.png" alt-text="Screenshot shows scope action's Settings tab, run after section, and selected action statuses that run the scoped actions.":::
0 commit comments