Avoid unintended node deletions

[mlauber71]

@dnguyen welcome to the KNIME forum. Sorry to hear about your troubles.

One thing you could do is build yourself some simple backup system to store versions of your workflow as a simple ZIP file with a timestamp (not super fancy but effective):

Copy/Move Files Node

@zedleb I created and example where the KNIME workflow (or workflow group) is being zipped into a file with a current timestamp. And can later be restored to a (separate) folder. [image] [image] This restore can either be automated also or you could do it manually if you need it. [image] [image] Please note you will have to configure the Path variables and workflow names to your needs. I use local paths that will be created dynamically.

Then backup and versioning is a thing in all businesses since all things that can go wrong might do so at any time. So regardless of KNIME or other tools it is always good to have a backup strategy ready. In the case of KNIME it is that the basic version does not have a recycle bin or a longer undo history. Although I understand that something might be on the agenda for the future (AP-11335). The KNIME server has a versioning and recycle option.

Restore Knime workflows

@evert.homan_scilifelab.se I can offer up these threads. Unfortunately if the workflows would not integrate themselves into KNIME like this you might have to revert to a backup. Can you tell us more about your system and the circumstance where the data is being stored (is it some sort of cloud drive?).