Thanks for the files, we’ll have a look.
The workflow.knime contains information about present nodes and connections in the top-most level of the workflow. Hence, I can see which nodes are referenced there and compare with the workflow.svg and the UI screenshot of the loaded workflow.
Many thanks, Manuel. Let me know if you need any additional info.
Three core devs stared at the files and screenshots you provided. We cannot explain why you were able to modify the old version so much without a problem, even executing all nodes – it is reallly puzzling. Based on the evidence, there was a desync between the UI and the backend, but we cannot find a reason why in the files.
Did you perhaps use “Save As” after you modified the old workflow?
We also found a UNC path \\<redacted>\users\Knime\ in the log that suggests that your workspace is located on a network drive, is that the case?
Also, there is a problem pointing to some Python extension in 5.3.2. Do you use the same workspace with multiple versions of KNIME? (5.3, then 5.4, then 5.3 again, etc.).
Yes, I do think I’d saved as since I leveraged an existing workflow (and kept some of the “downstream” nodes/processes intact as I adjusted & added new inputs). The workspace is on a network drive, and while I do recall some updates around this time, the workspace isn’t being used with multiple versions. We have multiple users running the same workflows that I build, but to do this I export a “production” version to a network location, and the others will import from there into their own workspaces.
In any event, I get the sense my issue is some odd combination of older workflow/save as/update. I hadn’t experienced previously, or since with some new workflows I’ve created. That said, if you find anything out or have some general guidance, that’s certainly appreciated.
Thanks much!
Good to know, thank you! We‘re investigating this problem internally and will post when we find something.
Rest assured that we take bugs leading to data loss very serious. It is just sometimes nontrivial to investigate if steps to reproduce are unknown. But your response greatly helps to narrow it down, thanks again!
We actually have plans for that 
Are you able to provide more details on that setup so we can try to reproduce?
First thing I’d personally do would be to verify that Save-As onto a network drive works correctly. Maybe you can try that on your setup.
Another interesting would be to use a mapped drive instead of the UNC path. Windows allows you to assign a drive letter (like the C: we all know) to a UNC path, see e.g. here on how to do that. Then point your Analytics Platform to the workspace at the path with the drive letter (you can copy it from the Windows Explorer).
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.