# GTDB-Tk jobs remaining queued for several days on usegalaxy.eu

**URL:** <https://help.galaxyproject.org/t/gtdb-tk-jobs-remaining-queued-for-several-days-on-usegalaxy-eu/18291>\
**Category:** usegalaxy.eu support\
**Tags:** server-status\
**Created:** [August 18, 2026, 2:32pm UTC](https://help.galaxyproject.org/t/gtdb-tk-jobs-remaining-queued-for-several-days-on-usegalaxy-eu/18291 "2026-08-18T14:32:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Raul\_Carlos\_Mainar\_J](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/raul_carlos_mainar_j/32/5667_2.png) [@Raul\_Carlos\_Mainar\_J](https://help.galaxyproject.org/u/Raul_Carlos_Mainar_J)\
**Post date:** [August 18, 2026, 2:32pm UTC](https://help.galaxyproject.org/t/gtdb-tk-jobs-remaining-queued-for-several-days-on-usegalaxy-eu/18291/1 "2026-08-18T14:32:26Z")

</div>

Hello,

I am running a MAG analysis workflow on Galaxy Europe and I currently have several GTDB-Tk Classify genomes jobs that have remained in **queued** state for several days.

I am using:

- Galaxy Europe (`usegalaxy.eu`)
- GTDB-Tk Classify genomes
- Tool version: **2.6.1+galaxy0**
- Input: collections of MAG bins generated with MetaBAT2

The previous steps of the workflow (assembly, mapping, MetaBAT2, CheckM and CheckM2) complete normally. Some GTDB-Tk jobs have eventually completed, but many others remain queued without starting, and I still have a large number of samples to analyse.

For the queued jobs:

- Job State: `queued`
- Standard Output: empty
- Standard Error: empty
- No exit code is generated, so the jobs do not appear to have started.

Could you please confirm whether there is currently a **GTDB-Tk resource/queue backlog on Galaxy Europe**?

I would also like to know whether you recommend simply leaving these jobs queued, or whether there is currently another recommended way to run GTDB-Tk for a large number of MAG samples.

I provide Job API ID as a example:

| Job API ID | 4838ba20a6d86765e8a3219f2ce61362 |
| --- | --- |

and can provide history links or workflow invocation links if needed.

Thank you very much for your help.

---

<div class="post-metadata">

**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:** [August 18, 2026, 5:04pm UTC](https://help.galaxyproject.org/t/gtdb-tk-jobs-remaining-queued-for-several-days-on-usegalaxy-eu/18291/2 "2026-08-18T17:04:20Z")

</div>

Hi @Raul_Carlos_Mainar_J

There were some server changes that may explain your queue behavior.

> [@Job delays at UseGalaxy.eu Aug 18 2026: Resolved, please leave queued jobs queued + rerun errors](https://help.galaxyproject.org/t/job-delays-at-usegalaxy-eu-aug-18-2026-resolved-please-leave-queued-jobs-queued-rerun-errors/18292/3):
>
> Sorry for the inconvenient. We have done some changes that had some unexpected repercussions.
> 
> You should be able to run jobs now (:

I would leave the jobs queued unless the administrators state that a rerun is needed. They will usually be able to get the existing backlog of queue jobs to process. But let’s see what they recommend this time.

Hi @Gabriel, do you have a recommendation?

General advice: this topic shows how to see the job queue. → [GTDB-Tk, reference data, and job queues: leave jobs queued for this competitive cluster group! - #2 by jennaj](https://help.galaxyproject.org/t/gtdb-tk-reference-data-and-job-queues-leave-jobs-queued-for-this-competitive-cluster-group/18237/2)

RIght now, I see about 400 queued with about 10-12 running at any particular time. How long this current queued group will take to process is difficult to predict since the read content, not just the file sizes, has an impact on runtime. It is more than it was a few weeks ago which may reflect some of the other issues on the server or it could just be more people coming back from summer break and starting new projects!

 ![Screenshot 2026-08-18 at 10.09.13 AM](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/6/6fc5909a4c7b6c2b9fd9e8bb00d5a4c9e36c22f4.png)  
 ![Screenshot 2026-08-18 at 10.09.52 AM](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/c/c008c3a12c6475adfdd549a6ecd98cbce8c924d4.png)

Thanks! 🙂

---

<div class="post-metadata">

**Author:** ![Gabriel](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/gabriel/32/8331_2.png) [@Gabriel](https://help.galaxyproject.org/u/Gabriel)\
**Post date:** [August 19, 2026, 7:17am UTC](https://help.galaxyproject.org/t/gtdb-tk-jobs-remaining-queued-for-several-days-on-usegalaxy-eu/18291/3 "2026-08-19T07:17:44Z")

</div>

> [@Raul\_Carlos\_Mainar\_J](#):
>
> 4838ba20a6d86765e8a3219f2ce61362

I would leave it in the queue. We are experiencing a general high volume of jobs.

Your tool in specific, according to our rules, require 200GB of memory to run. This is a lot of resources and it will take some time to find a slot within our scheduler.

---

<div class="post-metadata">

**Author:** ![Raul\_Carlos\_Mainar\_J](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/raul_carlos_mainar_j/32/5667_2.png) [@Raul\_Carlos\_Mainar\_J](https://help.galaxyproject.org/u/Raul_Carlos_Mainar_J)\
**Post date:** [August 19, 2026, 8:57am UTC](https://help.galaxyproject.org/t/gtdb-tk-jobs-remaining-queued-for-several-days-on-usegalaxy-eu/18291/4 "2026-08-19T08:57:04Z")

</div>

Thank you Gabriel!

Raúl

---

<div class="post-metadata">

**Author:** ![Raul\_Carlos\_Mainar\_J](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/raul_carlos_mainar_j/32/5667_2.png) [@Raul\_Carlos\_Mainar\_J](https://help.galaxyproject.org/u/Raul_Carlos_Mainar_J)\
**Post date:** [August 19, 2026, 8:58am UTC](https://help.galaxyproject.org/t/gtdb-tk-jobs-remaining-queued-for-several-days-on-usegalaxy-eu/18291/5 "2026-08-19T08:58:15Z")

</div>

Thank you for your replay.

I will keep the queued jobs.

Best,

Raúl
