# Launched jobs that never start, since 6th October 2025 **URL:** \ **Category:** usegalaxy.eu support\ **Tags:** troubleshooting\ **Created:** [October 7, 2025, 3:30pm UTC](https://help.galaxyproject.org/t/launched-jobs-that-never-start-since-6th-october-2025/16361 "2025-10-07T15:30:15Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Silke\_Jensen](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/silke_jensen/32/4847_2.png) [@Silke\_Jensen](https://help.galaxyproject.org/u/Silke_Jensen)\ **Post date:** [October 7, 2025, 3:30pm UTC](https://help.galaxyproject.org/t/launched-jobs-that-never-start-since-6th-october-2025/16361/1 "2025-10-07T15:30:15Z")
Hi, Since yesterday, 6 October 2025, I have been having trouble running tasks on [https://nanopore.usegalaxy.eu](https://nanopore.usegalaxy.eu). When I launch a task (Minimap2, Filter fasta), it remains greyed out for more than 24 hours. I had to relaunch these tasks today. Three of the five tasks worked and started running after a short period of time. I had to restart the other two because they remained greyed out and did not start. When I restarted the exact same task (using the ‘Re-do’ button), they were finally executed. No error messages appeared, and the tasks remained greyed out (and not blue). Thanks for your help ! ---
**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\ **Post date:** [October 7, 2025, 5:12pm UTC](https://help.galaxyproject.org/t/launched-jobs-that-never-start-since-6th-october-2025/16361/2 "2025-10-07T17:12:52Z")
Hi @Silke_Jensen 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. > [@How to see the UseGalaxy.eu job queue statistics](https://help.galaxyproject.org/t/how-to-see-the-usegalaxy-eu-job-queue-statistics/11837/2): > > If a job is still executing (yellow/orange) then that means it is still running. It is usually best to let those complete. [Troubleshooting resources for errors or unexpected results](https://help.galaxyproject.org/docs?topic=42) > > * * * > > ⏰ When working at [UseGalaxy.org](http://usegalaxy.org/), [UseGalaxy.eu](http://usegalaxy.eu/), or [UseGalaxy.org.au](http://usegalaxy.org.au/), your analysis jobs execute [at large scale academic clusters](https://training.galaxyproject.org/training-material/faqs/galaxy/#analysis). Hundreds of thousands of jobs process each month! > > - Use a [Workflow](https://training.galaxyproject.org/training-material/search2?query=workflow) for batch work. > - Allow [queued (grey color) and executing (yellow) datasets](https://training.galaxyproject.org/training-material/faqs/galaxy/datasets_job_status.html) to finish processing. > - Deleting and rerunning puts your job back _at the end_ of the queue again! > - Job priority is the exactly the same for everyone. > - **Be patient**. Galaxy is a free service, when a lot of people are using it, [you may have to wait longer than usual](https://training.galaxyproject.org/training-material/faqs/galaxy/analysis_jobs_not_running.html) (especially for ‘big’ jobs, e.g. alignments). > > * * * > > The EU server has a link to what the server is processing at any particular time. Today, right now, there are over 200 STAR jobs running. Maybe some of those are yours 🙂 The other servers do not post these stats publicly yet but all look about the same. To learn if something more is going on at the server level, you can check [https://status.galaxyproject.org/](https://status.galaxyproject.org/). > > * * * > > **Screenshots of EU server stats** > > ![Screen Shot 2024-03-04 at 2.08.02 PM](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/7/776bf9b831076661785156dadaedb221af32d26c.png) > > ![Screen Shot 2024-03-04 at 2.06.53 PM](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/7/7b81b451cb7aba2342cbe22a5967144e8ff63c10.png) > > * * * > > So, everything seems to be what is expected right now. I would suggest waiting for things to process. If you end up with some errors later on, and you need help interpreting the job logs, we can try to help more 🙂 * * * 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! 🚀 ---
**Author:** ![Silke\_Jensen](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/silke_jensen/32/4847_2.png) [@Silke\_Jensen](https://help.galaxyproject.org/u/Silke_Jensen)\ **Post date:** [October 8, 2025, 12:16pm UTC](https://help.galaxyproject.org/t/launched-jobs-that-never-start-since-6th-october-2025/16361/3 "2025-10-08T12:16:12Z")
> [@How to see the UseGalaxy.eu job queue statistics](https://help.galaxyproject.org/t/how-to-see-the-usegalaxy-eu-job-queue-statistics/11837/2): > > [Troubleshooting resources for errors or unexpected results](https://help.galaxyproject.org/docs?topic=42) Hi @jennaj Thank you very much for your detailed response and information. In the meantime, I think there was another problem. It was as if my jobs were never queued, because other jobs (the same Minimap2) did not wait long to run shortly after. I have several years of experience with Galaxy and have never encountered this kind of problem, except when our local Galaxy server restarted or crashed. It seemed more like a bug caused by the large number of jobs in the queue. Anyway, my jobs are done now 🙂 Many thanks for your help ! ---
**Author:** ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)\ **Post date:** [October 8, 2025, 5:05pm UTC](https://help.galaxyproject.org/t/launched-jobs-that-never-start-since-6th-october-2025/16361/4 "2025-10-08T17:05:57Z")
> [@Silke\_Jensen](#): > > It was as if my jobs were never queued, because other jobs (the same Minimap2) did not wait long to run shortly after. The only other part of this that I can think of is that the public servers have “server level” job queues, but also “account level” and “tool-level” job queues. These concurrency limits are custom/responsive based on administrative configurations. The public servers might have different rule sets than a local cluster. But, that said, maybe there was some small issue, and they reset something! They watch the discussions here, so asking is always Ok, and if anything is big enough to need special instructions we can address it (possibly needing the specific job details via a shared history)! In any case: queued jobs would still get priority if they needed to reboot. So, while asking, leaving the jobs “as-is” is what I would recommended while we discuss here. And, thanks for letting us know your jobs completed!! 🚀