The Product Idea boards have gotten an update to better integrate them within our Product team's idea cycle! However this update does have a few unique behaviors, if you have any questions about them check out our FAQ.

Alteryx Designer Desktop Ideas

Share your Designer Desktop product ideas - we're listening!
Submitting an Idea?

Be sure to review our Idea Submission Guidelines for more information!

Submission Guidelines

Step into Macro Debugging

There needs to be a way to step into macro a which is component of parent workflow for debugging.


Currently the only way to achieve to debug these is to capture the inputs to the macro from the parent workflow, and then run the amend inputs on the macro. For iterative / batch macros, there is no option to debug at all. This can be tedious, especially if there are a number of inputs, large amounts of data, or you are have nested macros.


There should be an option on the tool representing the macro in the parent workflow to trigger a Debug when running the workflow, this would result in the same behavior when choosing 'Debug' from the interface panel in the macro itself: a new 'debug' workflow is created with the inputs received from the parent workflow.


On iterative / batch macros, which iteration / control parameter value the debug will be triggered on should be required. So if a macro returns an error on the 3 iteration, then the user ticks 'Debug' and Iteration = 3. If it doesn't reach the 3rd iteration, then no debug workflow is created.

15 - Aurora

A step-through-macro-debugger would be a huge help, similar to Microsoft Visual Basic debugging.

Right now, macros are essentially a "black box", and are very difficult to debug.


These two options are helpful to debug macros:


1) Designer > View > Interface Designer > Test View (the magic wand icon on the left hand side) > input your values > Open Debug.
This will create a new standard workflows with the actual values coming from your inputs.
A copy of the workflow will open called Debug Workflow# (# being some number)
You can use the Debug mode to test what values are passed from the app interface to the workflow


2) Community > Blogs > Engine Works Blog > The X-Ray Browse: Macro Debugging Made Easier
Designed primarily for developing & debugging macros, the X-Ray Browse enables you to pick a location within a macro under development, to view the data passing through said macro at said location. The effect is similar to a Browse tool, but the data is made viewable through the encapsulating "skin" of the macro being developed.

Gallery Download link for X-Ray Browse Macro:!app/X-Ray-Browse-Macro/546263f9398a7111307b0cdc


14 - Magnetar
14 - Magnetar

Some of the tips here would be helpful:

I agree with the OP that debugging is not intuitive or possible, and doing it in coding languages where you can step through is much easier. 

12 - Quasar

it also can see some little bit messages via config > runtime.


but, i wish to have a function to view how each iteration is happen.


it easier to see what happen, and helpful to build macro as well.


i had post this idea before. at View Macro each iteration Result - Alteryx Community

Alteryx Alumni (Retired)

hi @braggis thanks for your feedback. We appreciate all the feedback we get and are working to review and respond to all ideas that have met the criteria to be brought to our product team.

Alteryx Community Team
Alteryx Community Team
Status changed to: Accepting Votes