SHAUN WEBB wrote:
Hi, I have a large number of files in a Galaxy library that are stored externally using the upload from file path and setting copy to galaxy to no.
A few times it has been necessary to rename or remove these files. I find that if the file was associated with a Galaxy history then that history is no longer accessible and produces a server error. I realise the best option is to keep copies of these files so that Galaxy histories remain consistent. However, it might be more user friendly if the particular history dataset displayed an appropriate error message and the rest of the history was still accessible.
Thanks Shaun Webb
Hi Shaun, This is not intentional. The history should still display, and the only noticeable difference is that the 'eye' and file save links would result in an error. Could you provide the error that's generated when this history display problem happens? Thanks, --nate