In a For Each scope, how is a message collection processed?

In a For Each scope, how is a message collection processed?

• A. Splits a message collection and processes the individual elements, then returns the original message
• B. Splits a message collection and processes the elements but does not return the original message
• C. Aggregates the results after processing
• D. Is only used in non-batch flows

Answer: (A)

For Each takes a message whose payload is a collection, splits it into individual items, and processes each item in turn. During each iteration, the current item becomes the payload so you can operate on it directly. After all elements are processed, Mule returns the original message to the flow, not an aggregated set of results. If you need to combine results from each iteration, you’d add a separate aggregation step or accumulate values yourself. This behavior isn’t limited to non-batch flows, and it isn’t about automatically aggregating results—the scope simply processes each element and then hands back the original message.

For Each takes a message whose payload is a collection, splits it into individual items, and processes each item in turn. During each iteration, the current item becomes the payload so you can operate on it directly. After all elements are processed, Mule returns the original message to the flow, not an aggregated set of results. If you need to combine results from each iteration, you’d add a separate aggregation step or accumulate values yourself. This behavior isn’t limited to non-batch flows, and it isn’t about automatically aggregating results—the scope simply processes each element and then hands back the original message.