Great new Aaron W. , and it's long overdue.
Before this, debugging a loop meant seeing only the last iteration. If iteration 37 of 200 failed, you had to guess at the cause from the final state. That led to some awkward workarounds and i love that we can avoid those 😄
Few thoughts ( please tag appropriate team if possible)
For Large loops. If a loop runs thousands of iterations, how are they paginated or searched in the job view? Filtering to "iterations with errors only" would be a big help or to be able pass iteration number to directly jump there.
I would be good if we can search or filter by a value within an iteration, such as "show the iteration where order_id = 12345"? especially for for-each loop , that generate data pills for each fields.
Does the job API or the Insights dashboard expose iteration-level data, or only the UI?
Overall this is a real quality-of-life improvement, and I think it will cut troubleshooting time noticeably, especially for batch syncs. Thanks for sharing it, Aaron!