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
+31Lines changed: 31 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -299,6 +299,37 @@ To catch exceptions in a **Failed** scope and run actions that handle those erro
299
299
300
300
For limits on scopes, see [Limits and config](logic-apps-limits-and-config.md).
301
301
302
+
### Set up a scope with "run after" for exception handling
303
+
304
+
1. In the [Azure portal](https://portal.azure.com), open your logic app workflow in the designer.
305
+
Your workflow must already have a trigger that starts the workflow.
306
+
307
+
1. On the designer, [follow these generic steps to add a **Control** action named **Scope** to your workflow](/azure/logic-apps/create-workflow-with-trigger-or-action#add-action).
308
+
309
+
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:
310
+
311
+

312
+
313
+
The following list shows some example actions that you might include inside a **Scope** action:
314
+
315
+
- Get data from an API.
316
+
- Process the data.
317
+
- Save the data to a database.
318
+
319
+
1. Now define the "run after" rules for running the actions in the scope.
320
+
321
+
1. On the designer, select the **Scope** title. When the scope's information pane opens, select **Settings**.
322
+
323
+
1. If you have more than one preceding action in the workflow, from the **Select actions** list, select the action after which you want to run the scoped actions.
324
+
325
+
1. For the selected action, select all the action statuses that can run the scoped actions.
326
+
327
+
In other words, any of the chosen statuses that result from the selected action cause the actions in the scope to run.
328
+
329
+
In the following example, the scoped actions run after the **HTTP** action completes with any of the selected statuses:
330
+
331
+

0 commit comments