UiPath Documentation
maestro
latest
false
Maestro Orchestrate user guide

Looping

Configure looping in Maestro Orchestrate for sequential tasks where each step depends on a prior result, with guidance on multi-instance execution and collection iteration.

Same task over a list, one by one (sequential multi‑instance)​

Note:

Use when​

  • Tasks must occur in order.
  • Each step depends on a prior result.
  • Sequence integrity matters.

Pattern in simple words​

  1. Start.

  2. Service task with sequential multi‑instance: Reconcile transaction over the collection.

  3. End All reconciled.

    Note:

    Sequential mode preserves order.

    Other scenarios

  • Finance: Post invoice lines in sequence.
  • Insurance: Review claims in received order.
  • Healthcare: Process test results per patient.
  • Retail: Approve store returns sequentially.
  • Manufacturing: Inspect items per batch.

Same task over a list, all at once (parallel multi‑instance)​

Use when​

  • Items are independent.
  • Items are independent
  • Order does not affect outcome.

Pattern in simple words​

  1. Start.

  2. Service task with parallel multi‑instance: Run security scan for each server in the collection.

  3. User task: Review results.

  4. End Scan complete.

    Note:

    Use aggregation to collect per‑item outputs.

    Other scenarios

  • Finance: Client credit checks simultaneously.
  • Insurance: Evaluate multiple policies in parallel.
  • Manufacturing: Inspect multiple lines concurrently.
  • Retail: Update store prices at once.
  • Public sector: Review permits across districts together.

Nested repetition inside a subprocess​

Use when​

  • Two levels of iteration exist, such as batch and item.
  • You need a clean structure that keeps loops organized.

Pattern in simple words​

  1. Start.

  2. Subprocess with sequential multi‑instance: Inspect batch, one batch at a time.

    • Inside the subprocess: Service task with parallel multi‑instance: Inspect item for each item in the batch.
  3. End Batch complete.

    Note:

    Use sequential outer and parallel inner when batches must not overlap.

    Other scenarios

  • Finance: Process monthly statements with multiple entries.
  • Healthcare: Audit patients by department.
  • Retail: Reconcile store sales by region.
  • Manufacturing: Audit batches by product line.
  • Insurance: Review claims by policy group.

Loop node: combined output and variable scoping​

The Loop node iterates over a collection and aggregates the results from all iterations into a single combined output. You can reference this combined output directly in downstream steps, without any additional data transformation.

Variables inside a loop are scoped to each iteration. Each cycle's data is isolated: one iteration's variables are not accessible to another.

Note:

Nodes with multiple outputs inside a loop are not yet fully supported. If a loop body contains a node that produces multiple outputs, results may not aggregate as expected.

Was this page helpful?

Connect

Need help? Support(opens in new window)

Want to learn? UiPath Academy(opens in new window)

Have questions? UiPath Forum(opens in new window)

Stay updated