- Introduction
- Process modeling
- Process implementation
- Process operations
- Process monitoring
- Process optimization
- Licensing
- Reference information
Maestro user guide
Markers annotate BPMN tasks and call activities to convey intent, such as repetition or compensation. In Maestro, markers are for modeling clarity, except multi‑instance, which Maestro interprets at runtime.
| Type | What it means | Runtime note |
|---|---|---|
| Sequential | One item at a time, in order. | Preserves order; next item starts after the previous finishes |
| Parallel | Many items at once. | Items run concurrently. Order is not guaranteed. |
|
|
|
The task executes in parallel and waits for all runs to be completed successfully before continuing to execute the rest of the process.
The task executes each item in the list one by one, waiting for each to be completed successfully before starting the next one. Once all tasks are completed, the rest of the process continues executing.
Marks an activity as eligible for compensation (undo logic) in the diagram. Maestro does not execute compensation automatically at runtime. Implement any undo logic explicitly in your model.
- Use markers to clarify design intent, especially for stakeholders who are not aware of execution constraints.
- Only the multi‑instance marker changes runtime behavior in Maestro; other markers are visualization aids.
- Document the loop logic and any compensation approach elsewhere in the process model.
- Prefer named collections and clear item schemas to improve readability.
Read Multi‑instance implementation for how to configure and run multi‑instance work.
For more details about the BPMN elements supported in Maestro, read BPMN support.
