Skip to content

Commit efccaa2

Browse files
authored
Merge pull request #5938 from mendix/MvM-ErrorEvent
Update text around Error Event and Rollback
2 parents 5de9a6e + a1c970f commit efccaa2

File tree

1 file changed

+1
-1
lines changed
  • content/en/docs/refguide/modeling/application-logic/microflows-and-nanoflows/events

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ This event can only be used in **Microflows**.
1111

1212
## 1 Introduction
1313

14-
An error event defines where a microflow will stop and throw an error that occurred earlier. If you call a microflow, you may want to know whether any errors occurred within the microflow or not. This event throws the error again, so the caller of the microflow can catch them. You can control whether all database actions within the current transaction will be rolled back using error handling settings (for more information, see [Error Handling in Microflows](/refguide/error-handling-in-microflows/)).
14+
An error event defines where a microflow will stop and throw an error that occurred earlier. If you call a microflow, you may want to know whether any errors occurred within the microflow or not. This event throws the error again, so the caller of the microflow can catch them. When you use this event, all database actions within the current transaction will be rolled back (for more information, see [Error Handling in Microflows](/refguide/error-handling-in-microflows/)).
1515

1616
{{% alert color="warning" %}}
1717
You can only use an error event if an error is in scope: Studio Pro does not accept it if you connect the normal execution flow to an error event, because there would not be an error to pass back to the caller.

0 commit comments

Comments
 (0)