This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
ALTERYX INSPIRE | Join us this May for for a multi-day virtual analytics + data science experience like no other! Register Now
1 Day Left! - The Alteryx Community will be temporarily unavailable for a few hours due to implementation of the new SSO experience starting tomorrow at 5pm MDT. Please plan accordingly. For more information, read the blog.
I use the CReW list runner to run a number of Alteryx workflows every day. Some of these workflows contain the python tool, which has started giving errors since we upgraded to Alteryx 2019.2. If the Alteryx flow contains a python tool and is run through the list runner, I get the error "Internal Error: Unknown InitVar "IsDebugAnalyticApp". If I just run the workflow directly, everything works fine. Does anyone recognize this error? If yes, do you know how to resolve it?
I have some processes that use the same feature. I had no problem migrating to version 2019.2. I suggest that you copy the python code and delete the old python tool and put new from version 2019.2 and insert the code again and save.
copying the code to a new tool didn't work. For some reason the error sometimes disapears. I even have two idential flows, one of them works with the list runner, while the other doesn't. I've opened both in notepad to compare the xml, but I can't find any differences there. My next guess was that it had something to do with chached data, but the error occurs identically on two different machines, and keeps occurring after a restart.
For the first time I'm using ListRunner with a workflow that has has multiple instances of a macro with two Python tools and I get this error every time I use ListRunner..even when I try using just a single instance of the macro.
The only workaround I've been able to figure out so far is to copy the flow out of the macro and put that into the main workflow, so all the Python code is now in the main flow.