3 day+ queue time for Trinity Assembly

Hi @WilliamC

Your job has been continually queued for four days now? And the input datasets to that tool are green/ready to use?

If are you running a really large number of jobs, that might be possible. But if you are just running a few jobs, that seems unusual.

Xref: Troubleshooting resources for errors or unexpected results

Do this if you would like us to help more:

  1. Start up a rerun for the original job.
  2. Don’t delete that original! You want to keep your queue placement.
  3. Generate a share back a link to your history with the original and rerun job and we can try to help more. If you are not sure how, see that FAQ I linked above.

Different tools run on different clusters, and some clusters are busier that others. Why? Because they are already running computationally expensive jobs, they take longer to free up for new work. But things will run. Never delete and rerun in hopes that things will go quicker since the opposite will result!

Let’s start there :slight_smile: