Boundary events are used to handle exception events that occur throughout a process on a specific activity. When an interrupting boundary event is triggered, the activity is stopped and the flow of the boundary event is taken. When a non-interrupting boundary event is triggered, the flow of the boundary event runs in parallel with the normal process flow.
Web Modelers can assign the Boundary Events to Sub-Processes and Tasks when mapping processes on Graph Edit Mode.
This table explains the different characteristics and types of the Boundary Events:
| Boundary Events | Symbol |
|---|---|
| Event Characteristic | Interrupting: ![]() Non-Interrupting: |
| Event Type | None Message: ![]() Timer: ![]() Escalation: ![]() Conditional: ![]() Link: ![]() Error: ![]() Cancel: ![]() Compensation: ![]() Signal: ![]() Multiple: ![]() Parallel Multiple: |
See here to get more details about the BPMN Properties
The Boundary Events section will cover:
Need more help with this?
Visit the Support Portal













