maestro
latest
false
- Overview
- Process modeling
- BPMN
- Process implementation
- Process operations
- Process monitoring
- Process optimization
- Reference information
Maestro user guide
Last updated Jun 23, 2025
Special event types
The following event types can appear as intermediate, boundary, or end events, depending on usage. These events typically model waiting, signaling, exceptions, or off-page navigation. They are supported for modeling clarity in Maestro.
| Event types | Description | Typical use | Execution in Maestro |
|---|---|---|---|
| Timer | Waits for a specific time, duration, or cycle | Deadlines, delays, timeouts | |
| Signal | Broadcasts or receives a named signal across process boundaries | Loose-coupled notification | |
| Error | Interrupts the current activity or path due to an exception | Business errors, validation failures | |
| Link | Connects different parts of a process, often across pages | Improves readability, avoids long arrows |
- Timer Events: Use as intermediate or boundary events to represent time-based control (e.g., Wait 2 days, Escalate after timeout).
- Signal Events: Use to coordinate across disconnected paths or sub-processes. Avoid relying on signal order or delivery timing.
- Error Events: Use on boundary events to redirect the flow on failure. Also valid as end events when explicitly terminating with an error.
- Link Events: Always pair a throw and a catch. Useful for breaking up complex diagrams into readable sections.
Important: All of these events are supported in
Maestro for both modeling and execution, except where noted. Label each clearly to
reflect its business intent.
For more details about the BPMN elements supported in Maestro, see BPMN support.
