Step into Macro Debugging

[braggis]

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.

[ChrisTX]

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
https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Random-results-while-renaming-fields/t...

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.
https://community.alteryx.com/t5/Engine-Works-Blog/The-X-Ray-Browse-Macro-Debugging-Made-Easier/ba-p...

Gallery Download link for X-Ray Browse Macro: https://gallery.alteryx.com/#!app/X-Ray-Browse-Macro/546263f9398a7111307b0cdc

[cgoodman3]

Some of the tips here would be helpful:

https://www.altertricks.com/how-to/debugging-alteryx-analytic-apps/

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. 

[PangHC]

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

[CristonS]

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.

[Pratik5]

Hi Team, I would like to share my experience with you regarding the Debug mode. I think this could be more simplified -

When I open a debug workflow for any macro, I need to manually update all the inputs every single time to test new records. This is too time consuming.

For example -

Main Workflow:

Macro screenshot:

In the debug workflow I must update the parameters, plus I must update all such inputs manually (by downloading) to test new records.

It would be incredibly helpful if, upon opening the debug mode, the system could automatically capture all the inputs. For this logic, the Debug mode option must be upon the right click on the macro.