I was able to reproduce the error with the most current tool version but dropping down to the prior version seems to be working better (hasn’t failed yet the same way as the original run). There is likely some small configuration issue the administrators need to resolve. You do not need to wait! Instead, try toggling into the prior version to see if that also works for you.
Since this “used to work”, I would suggest checking the version of the tool that you used before and what you may be using now. Or, you can just use the version that works if that is enough?
If you were running this inside of a workflow, I would also suggest opening the workflow in the editor and making the version adjustment in there!
I’ve sent in a bug report to the server administrators from the red error dataset and included the URL to this Help topic in the comments. You can do the same to provide them with more details.
Thanks for reporting the issue! Let’s see what the administrators think!
Thank you very much for your detailed response and for taking the time to test and report this to the administrators!
To confirm, yes, I am using the public server (`workflow4metabolomics.usegalaxy.fr`).
Unfortunately, even after testing prior wrapper versions (including the ones that previously worked for me), I am still getting the exact same error on my end. Since this exact dataset processed without any issue a few weeks ago, it really seems to be an infrastructure or resource allocation issue related to the recent maintenance.
Hi Théo,
I’ll look into your current issue, would you mind sending an error report from Galaxy UI? On your failed dataset : tab “Error” → Section “Issue Report”.
Thank you, and thank you Jen for looking into it until now
