# Jobs running or queued for more than 48 hours **URL:** \ **Category:** usegalaxy.be support\ **Tags:** queued-gray-datasets\ **Created:** [February 20, 2025, 3:23pm UTC](https://help.galaxyproject.org/t/jobs-running-or-queued-for-more-than-48-hours/14804 "2025-02-20T15:23:04Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Maddy-UW](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/maddy-uw/32/6768_2.png) [@Maddy-UW](https://help.galaxyproject.org/u/Maddy-UW)\ **Post date:** [February 20, 2025, 3:23pm UTC](https://help.galaxyproject.org/t/jobs-running-or-queued-for-more-than-48-hours/14804/1 "2025-02-20T15:23:04Z")
Hi there, I have been trying to run some tools - FastQC, Trimmomatic, and CRISPResso2 from the usegalaxy.be server. FastQC jobs have been either running or queued since last Friday (~144 hours), Trimmomatic jobs have been queued since last Saturday (~120 hours), and CRISPResso2 jobs have been queued for ~24 hours. Could someone please help me troubleshoot this? Thank you! ---
**Author:** ![daniel\_n578](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@daniel\_n578](https://help.galaxyproject.org/u/daniel_n578)\ **Post date:** [February 20, 2025, 6:31pm UTC](https://help.galaxyproject.org/t/jobs-running-or-queued-for-more-than-48-hours/14804/2 "2025-02-20T18:31:17Z")
I am also experiencing the same issues. ---
**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:** [February 20, 2025, 7:25pm UTC](https://help.galaxyproject.org/t/jobs-running-or-queued-for-more-than-48-hours/14804/3 "2025-02-20T19:25:27Z")
> [@Maddy-UW](#): > > usegalaxy.be Hi @daniel_n578 and @Maddy-UW I see a message on the server about planned downtime but do not know of the current status. I’ve sent a message through the web form to the server admins. You both could do the same. Find this on the server homepage (click on the upper top left icon, then scroll down a bit). Let’s also ping them here. Hi @padge would you be able to let us know if anything special is going on right now on the server? While we wait for feedback, the best general advice I have is to leave the jobs queued. If you delete and rerun, that only places the jobs back at the very end of the queue. This can significantly extend wait time, and if done often enough, a job may never get the chance to execute. This guide does not list UseGalaxy.be yet, but probably should, and the same processing guidelines do apply. > [@Troubleshooting resources for errors or unexpected results](https://help.galaxyproject.org/t/troubleshooting-resources-for-errors-or-unexpected-results/42/1): > > ⏰ 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-orange) 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). * * * Thanks for letting us know about the delays! More soon after the BE team reads the messages in their time zone! If either or both of you want to share a history with the queued jobs, we can help to double check that all of the inputs are in a good usable state (now), and the BE admins might be able to check for your specific tools/versions when they reply (later). 🙂 ---
**Author:** ![Maddy-UW](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/maddy-uw/32/6768_2.png) [@Maddy-UW](https://help.galaxyproject.org/u/Maddy-UW)\ **Post date:** [February 20, 2025, 9:43pm UTC](https://help.galaxyproject.org/t/jobs-running-or-queued-for-more-than-48-hours/14804/4 "2025-02-20T21:43:36Z")
Hi @jennaj, Thank you so very much for your response! Just an update: Trimmomatic and CRISPResso2 are running smoothly now 🤞 FastQC is still taking a long time to run from the usegalaxy.be server but runs fine from the [usegalaxy.org](http://usegalaxy.org) server. Thank you again 🙂 ---
**Author:** ![B0r1sD](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/b0r1sd/32/6160_2.png) [@B0r1sD](https://help.galaxyproject.org/u/B0r1sD)\ **Post date:** [February 21, 2025, 8:17am UTC](https://help.galaxyproject.org/t/jobs-running-or-queued-for-more-than-48-hours/14804/5 "2025-02-21T08:17:41Z")
Hi all Thank you for reporting this. We had to delete stuck FastQC jobs yesterday as they were the ones keeping your jobs in queue. We are in the process of identifying the issue with FastQC; it is our top priority today. We will give an update as soon as it is fixed. Your non-FastQC jobs should have run since. Apologies for the inconvenience! Kind regards Boris from useGalaxy.be ---
**Author:** ![B0r1sD](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/b0r1sd/32/6160_2.png) [@B0r1sD](https://help.galaxyproject.org/u/B0r1sD)\ **Post date:** [February 21, 2025, 2:50pm UTC](https://help.galaxyproject.org/t/jobs-running-or-queued-for-more-than-48-hours/14804/6 "2025-02-21T14:50:45Z")
The problem has been identified (by @padge) and is getting fixed as we speak. An update will be officially communicated on the useGalaxy.be frontpage.