maestro
latest
false
  • Overview
    • Introduction to UiPath Maestro™
    • Requirements
    • Example scenarios
  • Process modeling
  • BPMN
  • Process implementation
  • Process operations
  • Process monitoring
  • Process optimization
  • Reference information
UiPath logo, featuring letters U and I in white

Maestro user guide

Last updated Jun 24, 2025

Markers

Markers are small graphical notations added to BPMN tasks and call activities. They help document designer intent, such as repetition or compensation. In Maestro, markers are supported for modeling clarity only, except for multi-instance markers, which are interpreted at runtime.

Multi-instance markers

Multi-instance markers indicate that an activity should repeat for each item in a collection.
TypeDescriptionRuntime behavior
SequentialExecutes each instance one after anotherdocs image
ParallelExecutes all instances simultaneouslydocs image
Important: Must be configured with a collection input. Aggregation options may be configured if output is expected.

Looping support

To handle iteration-like tasks in Maestro (e.g., validating a list of items), you can use Parallel or Sequential markers. Markers behave like traditional loops, but they're more powerful, because they scale better.

These markers let Maestro dynamically fan out one task per item in the list — similar to a traditional forloop — while preserving scalability and observability.
Example:
You receive a list of invoice IDs from an external API. You need to validate each invoice by calling another API. Instead of writing a loop, you define a plan that contains:
  • a dynamic list of invoice IDs (from a previous step or external interrogation)
  • a parallel marker to fan out one action per invoice.

Compensation marker

Marks an activity as eligible for compensation (undo logic).
  • Modeling: docs image Not supported
  • Execution: docs image Not supported
Important: Use this marker when modeling transactional compensation scenarios. Execution logic must be implemented separately.

Modeling guidance

  • Use markers to clarify modeling intent, especially for readers unfamiliar with execution constraints.
  • Only multi-instance markers result in actual repeated execution.
  • Always document loop logic or compensation behavior elsewhere in the process.

For more details about the BPMN elements supported in Maestro, see BPMN support.

  • Multi-instance markers
  • Looping support
  • Compensation marker
  • Modeling guidance

Was this page helpful?

Get The Help You Need
Learning RPA - Automation Courses
UiPath Community Forum
Uipath Logo White
Trust and Security
© 2005-2025 UiPath. All rights reserved.