How to break ForEach loop in ADF

Question

How to break ForEach loop in ADF

Fasd 0

Hi everyone,

I have a ForEach activity containing a Copy Data task.

The Problem:

By default, if one iteration fails, the ForEach continues to trigger all other iterations. In my case, if the first one fails, the following ones are guaranteed to fail as well. I want to "exit" or "break" the loop immediately upon the first error to avoid unnecessary activity runs.

My current workaround:

To solve this, I'm using an If Condition inside the ForEach:

I check a variable status.

If status == 'Success', I run the Copy Data.

If the copy fails (red path), I set the status to 'Failed'.

This prevents the actual copy from running in subsequent iterations, but the ForEach still technically "runs" every item in the list.

My Question:

Is there a more "native" or "clean" way to stop a ForEach loop immediately when an error occurs? I'm looking to:

Avoid wrapping everything in an If Condition.

Physically stop the loop so it doesn't even "check" the remaining items.

Is there a setting I missed, or is switching to an Until activity the only true solution for a "hard break"?

Thanks!

SAI JAGADEESH KUDIPUDI 2,625 Reputation points Microsoft External Staff Moderator

2026-05-05T15:48:24.77+00:00
Hi Fasd,
in ADF today there isn’t a built-in “break” on the ForEach the way you’d have in a programming language, so you’ll need to simulate one. Here are a couple of patterns folks use:

Sequential + Fail activity • Set your ForEach to isSequential=true (batchCount=1). • On your Copy’s “On Failure” path, add a Fail activity. • As soon as one iteration fails, the Fail activity aborts the pipeline and no further loop items run.

Until loop pattern • Replace the ForEach with an Until activity driven by two variables: – errorFlag (boolean) – index (int) • Inside Until, check errorFlag == true or index >= arrayLength; if neither, execute your Copy/Data activity on item[index]. • On success: increment index; on failure: set errorFlag = true (and optionally Fail). • The Until will exit as soon as errorFlag flips, so you get a hard stop.

ExecutePipeline + Fail • Wrap your logic in a child pipeline that takes one item as a parameter. • In the parent pipeline’s ForEach, call that child via Execute Pipeline. • In the child, on error route, use a Fail activity—this bubbles up and halts the parent run.

If you don’t mind running everything sequentially and want a quick win, option #1 is usually the simplest. If you need more control or more complex branching, the Until-based approach gives you a true “stop on error” loop.

Hope that gives you some options!

Reference list

• ForEach activity limitations & workarounds: https://learn.microsoft.com/azure/data-factory/control-flow-for-each-activity#limitations-and-workarounds

• ForEach degree of parallelism: https://learn.microsoft.com/azure/data-factory/control-flow-for-each-activity#parallel-execution

• Until activity guide: https://learn.microsoft.com/azure/data-factory/control-flow-until-activity

• Fail activity: https://learn.microsoft.com/azure/data-factory/control-flow-fail-activity
Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

1 answer

Your answer

Answer 1

Hi ,

Thanks for reaching out to Microsoft Q&A.

there is no native “break” or “fail-fast” option in a ForEach activity in Azure Data Factory or Fabric pipelines.

ForEach is designed to be resilient and independent per iteration, so even on failure it will continue scheduling remaining items (especially in parallel mode). What you are doing with a status variable + If Condition is the standard workaround, but as you observed, it does not truly stop execution, it only skips logic.

If you need a true “hard stop” (stop further iterations from even triggering), the only clean pattern today is to replace ForEach with an Until loop where you control the index and exit condition explicitly. In that design, you can fail fast and break the loop immediately when an error occurs. Another partial option is to set ForEach to sequential (batch count = 1) and let the pipeline fail on first error, but even then it does not behave like a strict break control.

Bottom line: no native break; Until is the only proper fail-fast pattern.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.

Share via

How to break ForEach loop in ADF

1 answer

Your answer