Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

Alteryx Designer Desktop Discussions

Find answers, ask questions, and share expertise about Alteryx Designer Desktop and Intelligence Suite.
SOLVED

Alteryx 2019.2 Crashes after running workflow with embedded macro

nrossin
8 - Asteroid

We recently updated Alteryx to v2019.2.5.62427 and have had a lot of problems since.

 

The most recent issue is a predictable crashing of Alteryx altogether after running a workflow that contains an embedded macro. Neither the workflow nor the macro are at all complex as they only deal with formatting the input dataset (no analytics or even output yet).

 

Even a super basic workflow like this is problematic:

 

nrossin_3-1582826706629.png

 

 

Here is the embedded macro (which is just meant to parse a name field into first/last name fields and return the results):

 

nrossin_1-1582825995456.png

 

I have attached the embedded macro and sample workflow here.  

 

When the macro is included, the workflow completes successfully and I can browse the datastream until I click on the macro (so as to check its output). At that point, Alteryx freezes and crashes:

 

nrossin_2-1582826177783.png

 

This is a consistent crash whenever this macro is included in any workflow. Running the macro itself with a text input for the Macro Input works just fine as well.

 

I was not able to find any logs regarding the errors in the C:\ProgramData\Alteryx folder. 

 

 

2 REPLIES 2
fmvizcaino
17 - Castor
17 - Castor

Hi @nrossin ,

 

Sometimes when you save a workflow or a macro, if you do anything before the saving is complete, the xml file behind the workflow could be somehow corrupt in some way. 

https://community.alteryx.com/t5/Alteryx-Designer-Discussions/Error-opening-yxmd-file/td-p/7291

I know that it happens due to a problem I had in a customer of ours but I'm not sure why.

 

I was not able to find the exact problem in your xml, but since the problem was  happening when clicking in the macro, I deduced it was related to the macro input and output, so I erased both of then and inserted brand new ones.

 

Take a look and test it. 🙂

Best,

Fernando Vizcaino

nrossin
8 - Asteroid

Thank you, Fernando. This perfectly resolved the issue. I'm not sure what happened, but next time I'll compare my corrupted/working XMLs to see what actually changed.

 

 

Labels