I am currently working on a Batch Macro with a Python tool that writes to a certain output path based on the user's specifications. For the purposes of the overall workflow, we have the Python in the module set to Production Mode, and the overall workflow set to "Cancel Running Workflow on Error".
The python macro works as expected when set to Interactive Mode: however, when set to Production Mode, it seems that the progress updates pushed by the Python tool result in an error for the workflow, shutting it off. Is there a way to suppress these progress bar errors or disable them from appearing?
Hey @jsganga
I don't have a solution for you - we typically just leave Python in Interactive mode because we've seen some differences in the way that the Python tool runs across the two modes.
If you're able to mock up a simple case that demonstrates this difference - I'm pretty sure that the Support team would be keen to know - support@alteryx.com
Hi jsganga,
Did you find a solution to this? I get a similar issue with both ydata_profiling and sweetviz despite the file being written out (seemingly ok).
Hi @jsganga & @Mogul1 I am not sure what you are using in your workflow but I have supressed warnings, etc. using the following:
import warnings
warnings.filterwarnings('ignore', message='.*initial implementation of Parquet.*')
where you can filter the message type in the bold text.
Maybe give it a go?
Personally not seen progress bars come through as errors before...

