Deprecated legacy workflow retained for existing canvases only. Build cumulative or sequential batches where each loop iteration can use values produced by earlier iterations. Build every new repeated row workflow with List Iterator instead.
Where: Select a loop Group → Group settings; edit the driving Items card
Key ideas
- Deprecated—do not use for new work: Group Repeater, loop groups, Group Batch mode, and legacy Batch frames have been replaced by the source Items List → body → Results List pattern.
- Compatibility is read-only guidance: The legacy frame, its bindings, previous-results feed, and run controls are documented only so an existing canvas can be understood, repaired, and migrated without losing behavior.
Steps
- Do not create this workflow for new work. Open the List Iterator guide and build a paired source Items List and Results List instead.
- Use these legacy controls only when an existing canvas already contains the deprecated frame and must be inspected, rerun, or repaired.
- Record the old source rows, shared and per-item bindings, typed outputs, earlier-results dependency, nested scope, and result-history behavior before migrating.
- Rebuild the workflow as source Items List → body nodes → Results List, connect it with List Iterator, compare a small run with the legacy output, and remove the old frame only after the results match.
Legacy MCP tools
create_batch, create_loop_from_prompt, derive_items_for_loop, set_batch_bindings, run_batch, and create_group with is_loop=true exist only for old canvases. MCP hosts and the Flowgen assistant must use create_list_iteration, set_list_iteration, run_list_iteration, and select_list_history for new work.
Tips
- Keep the accumulated value compact or extract only the fields the next iteration needs.
- Test cancellation/retry semantics so a failed row does not silently pollute later context.
Limitations and important notes
- Deprecated: no new authoring should depend on Group Repeater, loop-group, or legacy Batch controls.
- Compatibility is preserved for existing canvases; migration is deliberate rather than automatic.
Troubleshooting
A later iteration sees the wrong history
Confirm Items row order and that previous-results is mapped to the intended socket, then inspect the accumulated output after each completed row.