I am caught in an odd loop when I am able to locally run a workflow that seems to somehow be using the KNIME AP Core features extension in particular the error that says this extension is missing now looks like this image attached. However I am when I try to load the extension the option to “finish” the install never appears the platform just hangs. I am on 5.5.1.
The other oddity is this workflow runs perfectly fine even though it says the nodes are missing.
I can’t really share this workflow easily since it is doing API calls to some of our source systems but if anyone has struggled with this circular issue please let me know.
the issue started on our Production Hub once they upgrade to 5.5.2
I just noticed if I try to search for this extension manually it doesn’t show up but the prompt automatically is able to find it. so maybe it is an issue with the download location?
Actually, one other oddity. I was able to force and update to 5.5.2 by doing the forced update option. then the screen allowed me to install the Core AP extension but the prompt that the nodes were missing still appeared. I am wondering if this workflow is simply corrupt somehow.
Again, the workflow runs perfectly fine locally with no errors.
The AP Core feature comes bundled with the Analytics Platform feature, so it is not to be installed/uninstalled/updated. I don’t know what consequences your force-update will have, but I would revert this or update everything to 5.5.2.
Based on the weird node names, I think the workflow is corrupted. We’ve had this very elusive bug in the past. If I remember correctly, it went like this:
Extension is not installed
Workflow with nodes from this extension is loaded and the nodes are marked as missing
Missing nodes are copied (this includes if they are inside a component, not obvious)
Pasted in another workflow, the nodes from the missing extension are saved as “real” missing nodes, losing their connection to their nodefactory (the long ID that you can also find in the node’s Hub URL).
It was a bug we fixed in 5.5.1, so I wonder if your workflow is older.
You could attempt to fix the workflow by going into its folder in your workspace (have the workflow closed and not open in AP), find the settings.xml of the two nodes that contain MISSING MISSING as prefix (this name should be in the settings.xml as well). The factory-id of the two nodes should mention MissingNodeFactory, this needs to be replaced by org.knime.datageneration.counter.CounterGenerationNodeFactory and org.knime.datageneration.emptyfilecreato.EmptyFileCreatorNodeFactory, respectively.
Then the popup should no longer appear. Though I’m a bit puzzled why it executes successfully.
Oddly I do not see any nodes with the MISSING MISSING designation here. see folder screenshot. I am wondering if I simply need to recreate the workflow from scratch – no copy paste of any of the nodes or components and resave to see if it generates any errors.
