Alteryx IO Discussions

Customize and extend the power of Alteryx with SDKs, APIs, custom tools, and more.

All incoming anchors initialized, but plugin has errors.

mkhtran
9 - Comet

Is there a way to deal with custom tools throwing errors when other tools have errors?

 

I have a tool that does nothing except pass data through, and it is properly configured inside the workflow.

 

 

class MyTool(PluginV2):
    def __init__(self, provider: AMPProviderV2):
        self.name = "My Tool"
        self.provider = provider

    def on_record_batch(self, batch: pa.Table, anchor: Anchor) -> None:
        self.provider.write_to_anchor("Output", batch)

    def on_incoming_connection_complete(self, anchor: Anchor) -> None:
        pass

    def on_complete(self) -> None:
        pass

 

Untitled.png

 

The problem is that is whenever a tool (custom or built-in) is added with an error, all my custom tools will throw an error too.

 

Untitled.png

The custom tool will throw the error "All incoming anchors initialized, but plugin has errors."

This is also annoying because deleting the Filter tool in this example won't remove the custom tool's error until the user interacts with it and causes a reinitialization.

2 REPLIES 2
aneeshnazar
Alteryx
Alteryx

Unfortunately, no - if there's an error upstream, the engine simply doesn't execute the python code. We don't currently have a way of passing that error into python

mkhtran
9 - Comet

This doesn't occur with just upstream errors. It occurs with downstream errors and even errors that are not connected to the main workflow as in the picture. This also seems to mostly occur for tools with required input anchors.