It takes about 5-10 seconds on average before something I click in the routine makes alteryx crash with no error message whatsoever. Are there any crash dump logs I can provide to get some assistance on why this is happening?
There doesn't seem to be anything wrong with the workflow itself or the specs of the machine. The machine never goes above 55% ram or CPU usage at any point, even when all data is loaded in the workflow (and it's not a lot of data anyway).
EDIT: Some extra info:
I was able to narrow the issue down a bit more but still no solution:
The workflow crashes only when I click on a specific batch macro that I'm using in it. As soon as I click (left or right click) on that macro or any of its anchors (1 input anchor 3 output anchors), in other words as soon as it's selected in any way, Alteryx gets stuck and crashes 3 seconds later with no error message/dialogue box whatsoever.
However, this happens only if the workflow was already executed at least once. If I just open the workflow and click on the macro before I execute, there are no crashes.
It's worth noting that the macro works fine and brings in the expected data (I can still use the workflow if i don't click the macro, and I can see that it produced correct data).
Anyone ever encountered something like this before?
@AkisM Try to uncheck the AMP Engine from the user settings and try again.
@binuacs It's already disabled.
I was able to narrow the issue down a bit more but still no solution:
The workflow crashes only when I click on a specific batch macro that I'm using in it. As soon as I click (left or right click) on that macro or any of its anchors (1 input anchor 3 output anchors), in other words as soon as it's selected in any way, Alteryx gets stuck and crashes 3 seconds later with no error message/dialogue box whatsoever.
However, this happens only if the workflow was already executed at least once. If I just open the workflow and click on the macro before I execute, there are no crashes.
It's worth noting that the macro works fine and brings in the expected data (I can still use the workflow if i don't click the macro, and I can see that it produced correct data).
Anyone ever encountered something like this before?