If the workflow configuration had a run for 'x' number of iterations option it would make debugging macros a lot easier. My current method consists of copying results, changing inputs and repeat until I find my problem which feels very manual.
fully agree with you @IraWatt
there's a lot that we could suggest for how to improve debugging of macros generally - like a way to manage the call-stack, and a way to simulate passing data between iterations without having to do all the work with files and interfaces.
This would be super useful, we currently have workarounds, but for iterative macros where successive rows rely on previous rows, the ability to see tool-by-tool how the second row is impacted by the first and so on would be helpful.
I'd very happy to see a this feature as well, especially because of the use of Engine.IterationNumber in my functions. I understand that there could be a workaround, maybe using additional columns and have their values progress in each iteration and then copying and pasting the iteration outputs into the inputs. However, I think it could get messy real quick, not to mention that it feels very ironic to do this manually with the goal of automation in mind.
