The job queues are expected. Please try to avoid deleting and restarting jobs since that only puts your job back at the end of the queue again. If you do this often enough, you job may never have a chance to move up the queue and actually run!
Example topic where this is explained, with many more under troubleshooting. In short, the public clusters are in use, are processing several thousands of jobs a day, and getting your jobs queued and left queued is how to effectively compete for the shared public resources!
A workflow is the fastest way to queue a lot of jobs all at once but you can still work tool-by-tool, just expect that to take a bit more time since that will be waiting for a person to start up the next tool, instead of streaming the work.
For today, for the Minimap2 statistics, there are about 10-12 jobs concurrently running and about 60 queued. The server is processing about 900 total jobs at any particular time.
The 60 queued will move into the ~10 processing as those cluster nodes are freed up by the current jobs. So, try to make sure your jobs are in that queued set or they won’t get a chance to run!
We hope this helps! 