’Unhandled Exception' When Opening Locked Workflow(Macro) with Python tools

Hi,

I created Macro with Python tools and Interface tools, and made it 'locked' to distribute it to others.

Unfortunately, when putting the locked Macro on canvas, it immediately shows 'Unhandled Exception Occurred' error, and doesn't show configuration window, either.

As far as I checked, if Macro does not contain the Python tools, it does not matter. Only when having the Python tools, locked workflow will have problem like this.

If any of you has the same/similar issue, appreciate sharing your thoughts or workaround. (Just knowing the fact that I'm not only guy suffering from this issue would help me.)

Designer: 2023.2.1.226(patch6)

Thank you in advance.

Workflow

Python

Macros

Accepted answers

All comments

flying008

Hi, @gawa

If you don't lock the macro, will it work properly?
I have some macros with built-in python tools, which are developed based on v2021~2022. There are no errors when using them. Of course, I didn't lock it.

gawa

hi @flying008 Thank you for question. Yes, macro itself works properly and configuration windows shows all interfaces configured.

Only when being locked, it causes error as described.

flying008

Hi, @gawa

BTW, you python tool within macro in design mode or product mode ?

gawa

hi @flying008 all of them are set to production mode.

flying008

Hi, @gawa

I just tested calling a macro containing Python tools after locking it, everything functioned correctly without errors.

There are two important points to consider:

1- Is the macro you created based on the AMP Engine or the E1 Engine ?

2- Does the Python library version used by your macro's version exactly match the Alteryx version used to call the locked macro?

gawa

@flying008

1) It's AMP. Regardless of AMP or E1, the same error happened.

2) Yes, it's no problem.

When I used 2022.3, I never faced this issue but it appears in 2023.2 suddenly.

flying008

Hi, @gawa

Maybe you can test the locked macro with v2024.1+ ?

BTW, what version when you lock the macro using? If you locked by v2022.3, try this lock step with v2023.2 again ?

gawa

It's solved. It was not because of Python.

When I created this macro, I copied and pasted from other WF, and convert all macro input tools to Text input tools. For some reason, these macro inputs tool configuration still persist in XML of yxmc after conversion, and caused error only when locked.

Thank you for continuous advice @flying008

Quick Links

This months top contributors

mceleavey 383

mbarone 337

Hollingsworth 335

LanisC 335

JeffF 335