Skip to content

Commit d57fa9e

Browse files
authored
Update control-flow-for-each-activity.md
Added multiple activity delay clause
1 parent c6fdc27 commit d57fa9e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/data-factory/control-flow-for-each-activity.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.reviewer: jburchel
88
ms.subservice: orchestration
99
ms.custom: synapse
1010
ms.topic: conceptual
11-
ms.date: 09/26/2024
11+
ms.date: 03/20/2025
1212
---
1313

1414
# ForEach activity in Azure Data Factory and Azure Synapse Analytics
@@ -214,7 +214,7 @@ In the ForEach activity, provide an array to be iterated over for the property *
214214
```
215215

216216
## Iterate over multiple activities
217-
It's possible to iterate over multiple activities (for example: copy and web activities) in a ForEach activity. In this scenario, we recommend that you abstract out multiple activities into a separate pipeline. Then, you can use the [ExecutePipeline activity](control-flow-execute-pipeline-activity.md) in the pipeline with ForEach activity to invoke the separate pipeline with multiple activities.
217+
It's possible to iterate over multiple activities (for example: copy and web activities) in a ForEach activity. In this scenario, we recommend that you abstract out multiple activities into a separate pipeline. Then, you can use the [ExecutePipeline activity](control-flow-execute-pipeline-activity.md) in the pipeline with ForEach activity to invoke the separate pipeline with multiple activities. If you iterate over multiple activities, there is potential delay in exiting the loop because of aggregation and cleanup work performed by the pipeline.
218218

219219

220220
### Syntax

0 commit comments

Comments
 (0)