# Jobs stuck in "queued" state for hours on usegalaxy.org (Filtlong and Seqtk seq) **URL:** \ **Category:** Uncategorized\ **Tags:** queued-gray-datasets\ **Created:** [October 17, 2026, 2:38am UTC](https://help.galaxyproject.org/t/jobs-stuck-in-queued-state-for-hours-on-usegalaxy-org-filtlong-and-seqtk-seq/18488 "2026-10-17T02:38:11Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Julian\_Vasquez](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/julian_vasquez/32/9067_2.png) [@Julian\_Vasquez](https://help.galaxyproject.org/u/Julian_Vasquez)\ **Post date:** [October 17, 2026, 2:38am UTC](https://help.galaxyproject.org/t/jobs-stuck-in-queued-state-for-hours-on-usegalaxy-org-filtlong-and-seqtk-seq/18488/1 "2026-10-17T02:38:11Z")
Hi everyone, I’m using galaxy .org and my jobs have been stuck in the “new / queued” state for more than 3 hours. Not a single job has started running. What I’m running: - Filtlong on a collection of 128 Nanopore FASTQ files (fastqsanger), with --min\_length 500 and --min\_mean\_q 8, all other options left at their defaults. - Seqtk seq (-A, force FASTA output) on the Filtlong output collection. What I see: - All elements are gray. The job info shows “new: This is a new dataset and not all of its data are available yet. queued”. - No job is red (failed) or paused, and there are no error messages. - I launched the same run a second time and it is also stuck in the queue. I [cancelled the duplicate run / left both running]. - My disk usage is [0% / 268.4 GB], so I don’t think quota is the cause. Questions: 1. Is there a known issue with the queue or the cluster right now? 2. Could running a 128-element collection at once be affecting my priority? Would it be better to launch it in smaller batches? 3. Is there anything else I should check on my side? Thank you very much for your help! Julian Vasquez ---
**Author:** ![Evan\_Olivares](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/evan_olivares/32/9069_2.png) [@Evan\_Olivares](https://help.galaxyproject.org/u/Evan_Olivares)\ **Post date:** [October 17, 2026, 9:28pm UTC](https://help.galaxyproject.org/t/jobs-stuck-in-queued-state-for-hours-on-usegalaxy-org-filtlong-and-seqtk-seq/18488/2 "2026-10-17T21:28:05Z")
Hello Julian, I’m also experiencing issues with Filtlong. For me, I’m trying to run a concatenated dataset of 114 FASTQ files through filtlong but it has been stuck in “queued” for two hours. Although I cannot say with confidence, I’m pretty sure theres an outage with Filtlong (since all tools in Galaxy work with external resources). I don’t know when it will come back, but I’ve previously ran a lot of files through Filtlong and this is definitely abnormal. Hope everything goes well and Filtlong works soon! Evan Olivares ---
**Author:** ![koffikon](https://avatars.discourse-cdn.com/v4/letter/k/d9b06d/32.png) [@koffikon](https://help.galaxyproject.org/u/koffikon)\ **Post date:** [October 20, 2026, 2:11pm UTC](https://help.galaxyproject.org/t/jobs-stuck-in-queued-state-for-hours-on-usegalaxy-org-filtlong-and-seqtk-seq/18488/3 "2026-10-20T14:11:00Z")
Hello Galaxy Support, I am experiencing a problem with a Galaxy job that has remained queued for an unusually long time. **Job details:** - Galaxy server: - Dataset ID: 11139 - Tool: Join two Datasets (Galaxy Version 2.1.3) - Input datasets: 11137 and 11138 - Job submitted: October 17, 2026 - Current status: Queued — “This job is waiting to run.” Both input datasets are successfully completed tabular files containing approximately 1.1 million rows each. The job has remained queued without starting. I have refreshed the Galaxy history and checked the job information, but the status has not changed. Could you please check whether there is a problem with the job scheduler or available computing resources? Should I continue waiting or resubmit the job? Thank you for your assistance. ---
**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 22, 2026, 12:22am UTC](https://help.galaxyproject.org/t/jobs-stuck-in-queued-state-for-hours-on-usegalaxy-org-filtlong-and-seqtk-seq/18488/4 "2026-10-22T00:22:02Z")
Hi @Julian_Vasquez @Evan_Olivares @koffikon For the #queued-gray-datasets , there isn’t anything special happening at [UseGalaxy.org](http://UseGalaxy.org) right now. The usual advice about confirming your inputs and leaving queued work queued will apply. Then, for [UseGalaxy.eu](http://UseGalaxy.eu) that is the same, and there is a dashboard where the exact status can be reviewed. → [How to see the UseGalaxy.eu job queue statistics](https://help.galaxyproject.org/t/how-to-see-the-usegalaxy-eu-job-queue-statistics/11837) with examples at [Search results for 'job statistics' - Galaxy Community Help](https://help.galaxyproject.org/search?q=job%20statistics). All public Galaxy servers will look about the same. * * * Status: a few hours is still a very short queue! If work is queued longer than a day, then we can help with a review here. - 🛠 The inputs, tool, parameters, and server can all matter for this. How to share your work with all of these details is in the banner topic, also here. → [FAQ: Sharing your History](https://training.galaxyproject.org/training-material/faqs/galaxy/histories_sharing.html) To avoid delays later on… - ⚙ [Workflows](https://help.galaxyproject.org/search?q=workflows) remain the best way to process batches of work. Most tutorials include [reusable workflow templates](https://training.galaxyproject.org/training-material/workflows/list.html). Once oriented, explore the [IWC Workflow Library](https://iwc.galaxyproject.org/) and try a **production workflow** for [streamlined batch analysis](https://iwc.galaxyproject.org/). Please let us know how this work turned out or if you would like a closer look! 🙂