18 months ago by
There may have been a connection issue triggering the metadata problem. Have you tried autodetecting the metadata and reviewing the output? In prior cases where metadata has been an issue with job runs, the output has been intact. Metadata issues are related to technical database content - not the actual result data content - and resetting that database content (metadata) allows the result to be accessed.
If you are concerned about the completeness of the run, I personally have not seen a Trinity job abort mid-execution, incomplete, and return with a metadata detection problem. The result would be an error message instead (in a red dataset). However, you could rerun anyway and compare the results.
Should a rerun show that the original result was incomplete (or anything else odd), we would want to investigate as this would be novel. Please send in an email with a shared history link to firstname.lastname@example.org. Improved error trapping would be one possible resolution. Make sure that all input and result datasets are undeleted (you can delete them once we get a copy) and include a link to this Biostars post so we can associate the two.
Trinity service is relatively new and has been problematic due to connection and related issues with the external site that executes the analysis, but we want to resolve those so we can continue to provide access to the service at http://usegalaxy.org. Improving usability on our side is the portion we can control.
Thanks for reporting the problem and our apologies for the trouble with this tool. Jen, Galaxy team