maestro
latest
false
- Introduction and getting started
- Maestro landing page
- Process modeling
- Process implementation
- Process operations
- Process monitoring
- Process optimization
- Licensing
- Reference information
Maestro user guide
Last updated Aug 12, 2025
Intermediate events model things that happen between the start and end of a process. They can delay the flow, wait for an input, or signal something to other elements.
| Event type | Icon | Usage |
|---|---|---|
| Message (Catching) | Waits for a message to continue. Placed inline or on a boundary. | |
| Timer | Delays flow until a timestamp or duration. Commonly used for timeouts. | |
| Signal (Throw/Catch) | Broadcasts or waits for a signal. Use to loosely couple process fragments. | |
| Link (Throw/Catch) | Used as off-page connectors. Improves readability in large diagrams. | |
| Escalation (Throw/Catch) | Indicates a business-level escalation. Typically attached to boundary events. | |
| Error | Represents an exception. Must be caught by an error boundary event on a task or sub-process. |
Important: In modeling, intermediate events should be used
to clarify dependencies or timing logic. The actual behavior may depend on runtime
support.
For more details about the BPMN elements supported in Maestro, see BPMN support.
