Support for Versioning in Nested Workflows and Resubmit Limitations in Logic Apps Standard

Question

Alex Boiko 0

I'm using Logic Apps Standard with nested workflows and have two questions:

How can I ensure the same versions of nested workflows are used when resubmitting from activities inside the parent workflow? This is crucial for maintaining consistency in our workflow executions.
Why is the resubmit button limited to workflows with fewer than 40 activities? Are there plans to increase this limit? This limitation is challenging for complex workflows with more activities.

Any insights or guidance would be appreciated. Thank you!

Locked Question. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

Christos Panagiotidis 3,546 Reputation points

2026-07-30T06:01:32.5566667+00:00

Logic Apps Standard does not provide an immutable, selectable workflow-version history equivalent to the Consumption version feature. When a run is resubmitted, the service uses currently deployed workflow definitions and connections, so a parent does not automatically invoke the historical child definition. If reproducibility is required, deploy each child release as a distinct versioned workflow name or app, have the parent call that explicit version, and retain the matching artifact in source control. Replay original input against that deployment instead of relying on portal resubmit. The portal’s resubmit restriction for runs with many actions is a service or interface limit, not an app setting that can be increased. Microsoft has not published a committed expansion date. For large workflows, split the orchestration into smaller workflows or implement a controlled replay endpoint that records correlation and idempotency data. Use Support only to investigate behavior that differs from the documented limit.

Christos Panagiotidis 3,546 Reputation points

2026-07-30T06:01:32.5566667+00:00

Logic Apps Standard does not provide an immutable, selectable workflow-version history equivalent to the Consumption version feature. When a run is resubmitted, the service uses currently deployed workflow definitions and connections, so a parent does not automatically invoke the historical child definition. If reproducibility is required, deploy each child release as a distinct versioned workflow name or app, have the parent call that explicit version, and retain the matching artifact in source control. Replay original input against that deployment instead of relying on portal resubmit. The portal’s resubmit restriction for runs with many actions is a service or interface limit, not an app setting that can be increased. Microsoft has not published a committed expansion date. For large workflows, split the orchestration into smaller workflows or implement a controlled replay endpoint that records correlation and idempotency data. Use Support only to investigate behavior that differs from the documented limit.