Internal Error: Unknown InitVar "JupyterTempPath"

Hi,

I'm trying to create workflow that will run periodically in the gallery, check for starting conditions and trigger further processing only when certain starting criteria are met.

To achieve this goal I split the logic into two separate workflows:

- Run_Python.yxmd to check starting conditions

- Python.yxmd process the data

Run_Python.yxmd is using "Conditionall Runner" CReW macro to start processing only when starting criteria are met.

The problem is that when running Python.yxmd in CReW macro, python component fails to start due to:

Internal Error: Unknown InitVar "JupyterTempPath"

Actual logic is very complex and can't be shared online.

Attached simplified workflows to demonstrate the issue.

Run_Python.yxmd Log parser output:

Module	ToolId	MessageType	Message
[Null]	[Null]	Message	Null]
Python	[Null]	Message	Alteryx Version: 2020.1.2.24185
Python	[Null]	Message	Started running .\Python.yxmd
Python	1	Error	Internal Error: Unknown InitVar "JupyterTempPath"
Python	3	Message	Message 1 record was output
Python	[Null]	Message	Message Finished in 1.6 seconds with 1 error

Please advice on how to fix this issue,

or how to conditionally start / stop workflows.

Python.yxmd

Run_Python.yxmd

Python

Macros

Accepted answers

All comments

Madzac

Hi Marcin,

Has this issue been solved? I have a similar issue on my workflows.

All the best,

FreeRangeDingo

Also having this problem....

YEM

Also having this problem.

Macro1 contains the python tool.

Workflow1 calls macro1, it works fine.

Put workflow1 in a runner, I get this error.

Birty

I raised this as an issue with Alteryx support - its a known defect in the later releases of Alteryx.

"This error is a known defect with the newer version of Designer while using the runner macros and calling a work flow that has a python tool in it. I have attached your case to the defect so once it has been worked out and fix you should get an automated email. However, I am not able to give you a timeframe of when that might happen since the development team is still working on road mapping it."

It worked fine with the 2019 releases - so broke sometime in 2020. I'm going to have to uninstall and re-install multiple versions of Alteryx to find the latest in which it worked, as I need some of the new functionality that emerged in the 2020 releases ...

andyjohnstone2

Hi Marcin / all

Wonder if this issue has been further understood. Have tried multiple different Alteryx versions from the latest back down to 2019 with no success.

Any approaches worth trying would be very appreciated.

Best, Andy

matt43582

I've run into this problem, too, and haven't tried this approach yet but I think it should work... what if you "wrapped" the python-using module in a workflow that just called the python-containing workflow using a batch command (~/<<alteryx engine executable>> <<your workflow>>) so that the CReW tool was indirectly calling your python workflow?

Sorry for the rough outline, but busy day and I can't guarantee I'll be able to find my way back to this thread. Going to try it, though.

Quick Links

This months top contributors

atcodedog05 19458

Qiu 15867

binu_acs 15708

MarqueeCrew 13708

apathetichell 13703