RESOLVED Trinity assembly waiting to run for >24h -- Extended job queue times at public Galaxy servers

[h.mckay]

My Trinity assembly has been waiting to run for more than 24 hours - is this normal? Should I cancel it and run it again? Please let me know if there is something going on with the server or if this is the normal time frame for running this tool.

Thanks!

[jennaj]

Please see this related post for details. In short, all public Galaxy servers are very busy and jobs are queuing a bit longer than usual. Avoid deleting/restarting for the fastest processing.

Trimmomatic Job Stuck in Queue -- Extended job queue timing across public Galaxy servers

Good evening, I had started a Trimmomatic job on a paired end dataset at about 1:10 UTC. It’s been nearly 3 hours now with the jobs stuck in queue. Are you currently experiencing a lot of traffic? Another question I had was how many jobs I could run concurrently? I was going to queue FastQC as well, but I’m unsure if queuing too many jobs might lead to an error. I apologize if the questions were a little basic, I’ve just started using Galaxy. Thanks for your time!