Hi, I have been having problems lately. The jobs do not run, being permanently on hold. Any suggestions? Thank you all.
I see one larger job queued since Sun 29 Jul 2018 01:15:09 PM (UTC). This was about three hours ago and is a normal amount of time to have a job queue (can take up to 24 hrs, depending on a few factors).
If the job stays queued longer than 24 hrs, first double check your inputs (appear to be Ok, but I didn't review all upstream jobs) and let us know. There are no known cluster issues that would impact this run at this time.
Thanks! Jen, Galaxy team
The jobs still remain queued at this point and I already checked my inputs and seem to be ok. Can you help me, please?
Thank you for all, André Pereira
Hello - I went through the inputs again and dataset 787 (hidden) has metadata problems. This causes downstream jobs to stay "on hold" until the input issues are resolved.
Choose to display hidden datasets in the history and you'll find the warning within the 787 dataset displayed in a yellow box. From there you can also review the content (empty). The autodetect link will not fix the data in your case as there was no output.
A rerun might work or you might need to adjust some inputs/parameters when creating the mothur.count_table data. The Mothur tool suite is covered in the Galaxy tutorials if you need usage examples/help: https://galaxyproject.org/learn/
Hope that helps! Jen, Galaxy team