we are running a local Galaxy (an older release) instance and encounter the following issue. After exporting history to file there is an "orphan" dataset left (in galaxy/database/files/...). It looks like it doesn`t belong to any history, thus the cleanup scripts cannot delete it. Of course, we can delete it manually via "rm", but it is usually not at all recommended.
Is there a recommended procedure to deal with it? I assume the most promising way would be to update our instance, but I would like to know whether someone already encountered this issue and solved it.