In case you missed the announcement: The Alteryx One Fall Release is here! Learn more about the new features and capabilities
here
ACT NOW: The Alteryx team will be retiring support for Community account recovery and Community email-change requests Early 2026. Make sure to check your account preferences in my.alteryx.com to make sure you have filled out your security questions.
Learn more here
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.