Skip to content

Commit c920e2e

Browse files
committed
Apply discussed changes to try to clarify error handling in microflows.
1 parent 724bab3 commit c920e2e

2 files changed

Lines changed: 33 additions & 25 deletions

File tree

content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/events/error-event.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,8 @@ When you use this event, it creates a new error of the type which occurred earli
1818
You can only use an error event if an error is in scope: Studio Pro does not allow you to connect the normal execution flow to an error event, because there would not be an error to pass back to the caller.
1919
{{% /alert %}}
2020

21+
## Example of Error Event
22+
2123
In the example below, an error flow is defined when committing an object to the database. Any error is caught, and the flow continues to the error event where the error is passed back to the caller of the microflow. This allows you to implement your error handling on multiple levels.
2224

2325
{{< figure src="/attachments/refguide/modeling/application-logic/microflows-and-nanoflows/events/error-event/error-event.png" class="no-border" alt="A microflow with a parameter of 'MyEntity'. It has a single action committing 'MyEntity' which has an error flow ending in an error event and the normal flow ending in an end event" >}}

0 commit comments

Comments
 (0)