---
title: Why Blueprint Creates Multiple Similar Subflows
slug: blueprint/why-blueprint-creates-multiple-similar-subflows
docTags: yO7XZ9PJxDCKZ-Mf4TSYB
createdAt: 2026-04-17T18:28:53.275Z
---

:::CtaButton{label="🟢 Migrator" openInNewTab="false"}

:::

During migration you may notice what appear to be duplicate subflows in your PAD output. This is intentional — each instance exists for a specific technical reason.

***

# Three Reasons Blueprint Creates Subflows

:::Heading{depth="2" indent="1"}
Direct Process Translation
:::

Sub-processes from the source automation (such as UiPath workflows) are recreated as discrete subflows in PAD to preserve the original logical structure.

:::Heading{depth="2" indent="1"}
Variable Management
:::

PAD handles variables differently than legacy RPA platforms. Blueprint creates wrapper subflows to manage how data passes between parts of the automation. See Wrapper Subflows for a full explanation.

:::Heading{depth="2" indent="1"}
One-to-Many Action Translation
:::

Some source actions have no direct PAD equivalent. Blueprint combines multiple PAD actions — loops, conditions, data operations — to replicate the same behavior. This is the most common reason you'll see subflows that look nearly identical.

***

# Why Similar Subflows Aren't Identical

When an action appears multiple times in the original automation, each instance has different specifics — different data sources, variable names, hardcoded values, or parameters. Because PAD lacks variable scoping, each instance requires its own subflow.

:::BlockQuote
**Example:** A UiPath process uses a GetNextItem action three times — once for a HighPriority queue, once for Standard, and once for LowPriority. The core logic is the same, but each call works with a different queue name, so Blueprint generates three separate subflows.
:::

***

# Why This Approach Works

- **Accuracy** — Each subflow is precisely tailored to its context, ensuring the automation behaves as intended
- **Maintainability** — Changes to one instance don't affect the others
- **Clarity** — Each subflow reflects exactly what it does in that specific context