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 Oct 4, 2025
A start event defines how a process begins. A diagram must include exactly one start event.
| Event type | Icon | Meaning |
|---|---|---|
| None | Used for manual starts or when the trigger is defined outside the BPMN model. | |
| Message | Indicates the process is triggered by an incoming message. Often used in called processes. | |
| Timer | Indicates the process starts at a specific time or after a delay. Useful for scheduled operations. |
A process in Maestro must include at least one start event. A Maestro process must include at least one start event. You can model multiple start events in the same process to support different entry points.
When you have multiple start events and you want to do a Debug, right-click the start event
you want to test and select Test.
When you deploy a process, you can set a default entry point (a start event).
Orchestrator uses this start event when you start the process without explicitly specifying
one. You can still run or debug from any other start event by selecting it at run time.
Note: A process in Maestro must include at least one
start event. You can model multiple start events in the same process to support different
entry points (for example FHTTP/API), schedule, or manual Use sub-processes to model
additional entry points.
For more details about the BPMN elements supported in Maestro, see BPMN support.
