4.2 years ago by
Mapping jobs go to our busiest cluster and it is not uncommon for these to queue in the 'waiting to run' state. The most effective way to run jobs when this happens is to leave the queued jobs to process - do not stop and restart. More here:
That said, two days is a bit long to wait. My guess is that these were started/restarted already one or more times, placing the new job at the back of the queue again. Or, that you had other jobs that were queued or running that were submitted before these, in the same history or another.
Jobs run in the order submitted, across your entire history. When the server seems to be busy, it is a good idea to submit your most important work first.
Good luck and hope this helps to explain how the queues work, Jen, Galaxy team