Pattern
Offload High-Volume Loops to a Flow Fan-Out
Agents that must loop through hundreds of questions stall or fail when the agent itself acts as the orchestrator.
Last reviewed 9 July 2026
The pattern
Do not make the agent loop through high-volume work itself. The agent is not your orchestrator for bulk processing. Instead, hand the work to a Power Automate fan-out pattern. The flow spreads hundreds of items across parallel processing. This avoids the agent stalling on long question loops. You keep the existing agent and add the flow as a tool. [UNSICHER: exact mechanics of the fan-out pattern in the source, e.g. how parallelism is configured]
When to use it
- You need to loop through hundreds of questions or items in one run.
- The agent stalls, times out, or repeats when driving a large loop.
- You want to avoid rebuilding the agent from scratch.
- Bulk processing should run outside the conversational turn.
Steps
- Identify the high-volume loop that is overloading the agent.
- Build a Power Automate flow that processes the item set.
- Structure the flow as a fan-out so items process in parallel rather than one long agent loop. [UNSICHER: the source's precise fan-out construction is not reproduced here]
- Attach the flow to the agent as a tool.
- Have the agent call the flow once, passing the batch, instead of looping itself.
- Return the aggregated result from the flow back to the conversation.
- Test with a representative high-volume input to confirm the agent no longer stalls.