Skip to content

Commit 7052d1d

Browse files
committed
Update Try Catch block
1 parent 3ee69db commit 7052d1d

File tree

2 files changed

+7
-12
lines changed

2 files changed

+7
-12
lines changed
-11 KB
Loading

articles/data-factory/tutorial-pipeline-failure-error-handling.md

Lines changed: 7 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -168,18 +168,13 @@ The pattern is a combination of two: conditional and + error handling. The pipel
168168
:::image type="content" source="media/tutorial-pipeline-failure-error-handling/conditional-complex-1.png" alt-text="Screenshot showcasing pipeline proceeds to next step if any of the activities pass, or else runs error handling code.":::
169169

170170

171-
#### Try-Catch-Proceed
172-
The pattern is equivalent to try catch block in coding. It states that if either the activity or the error handling code succeeds, the pipeline should proceed. It's rather complicated and should only be reserved for the most mission critical steps.
173-
* add the mission critical work step
174-
* add an error handling activity to the _"Upon Failure"_ path of the main activity
175-
* add an if condition to contain next steps, in True branch
176-
* connect _"Upon Completion"_ path of the main activity to the condition activity
177-
* connect both _"Upon Success"_ and _"Upon Skip"_ paths of the error handling activity to the condition activity
178-
* logical expression for condition activity reads
179-
```json
180-
@or(equals(activity('ActivityFailed').Status, 'Succeeded'), equals(activity('ErrorHandling').Status, 'Succeeded'))
181-
```
182-
* Note the order of expressions: the main activity part has to come first, before the error handling activity part
171+
### Try-Catch-Proceed
172+
The pattern is equivalent to try catch block in coding. It states that if either the activity or the error handling code succeeds, the pipeline should proceed. We have simplified and streamlined the implementation for our customers. Try catch block does not need an if block.
173+
174+
* Add first activity
175+
* Add error handling to the UponFailure path
176+
* Add second actvity, but do not connect to the first activity
177+
* Connect both UponFailure and UponSkip paths from the error handling activity to the second activity
183178

184179
:::image type="content" source="media/tutorial-pipeline-failure-error-handling/conditional-complex-2.png" alt-text="Screenshot showcasing pipeline with try catch block.":::
185180

0 commit comments

Comments
 (0)