# Flye jobs don't start **URL:** \ **Category:** usegalaxy.eu support\ **Tags:** queued-gray-datasets\ **Created:** [October 26, 2023, 9:53am UTC](https://help.galaxyproject.org/t/flye-jobs-dont-start/11048 "2023-10-26T09:53:08Z")\ **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 26, 2023, 9:53am UTC](https://help.galaxyproject.org/t/flye-jobs-dont-start/11048/1 "2023-10-26T09:53:08Z")
Hi all, since yesterday I have a problem with running “Flye” genome assembler on [https://nanopore.usegalaxy.eu](https://nanopore.usegalaxy.eu). It remains in the “This job is waiting to run” status for hours, while other tools start running without any problem, but only if I delete the blocked Flye job first. I would be grateful for any help. Thank you ! ---
**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 26, 2023, 4:49pm UTC](https://help.galaxyproject.org/t/flye-jobs-dont-start/11048/2 "2023-10-26T16:49:27Z")
Welcome, @Silke_Jensen Like most assembly tools, the **Flye** tool is computationally expensive. That means the job requires more resources, and will tend to run longer than other tools. When working at a public server, your own Flye jobs are running on shared resources _also_ used by others to run these larger and longer running jobs. So, some patience is needed. Practically, this means leaving the jobs “queued” and allowing them to run to completion. Each tool has different processing requirements … and that can include “upstream” jobs. There is a limit on how many _concurrent_ jobs each person can run. Getting jobs into the queue, then allowing them to complete, is the fastest way to process work for anyone. That is what a workflow will do for you. A workflow queues everything at once – then processes those jobs in a stream while you are away. If you are still in a pre-workflow stage, then the best advice is to queue up as much as you can, set a notification, then come back later. Deleting and rerunning jobs puts all new jobs at the very back of the queue, each time, and if done quickly enough no jobs may ever have a chance of processing! I’m adding some tags to your post that link to other similar Q&A. ---
**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 28, 2023, 12:57pm UTC](https://help.galaxyproject.org/t/flye-jobs-dont-start/11048/3 "2023-10-28T12:57:26Z")
Thank you very much for your reply. I understand better now. It’s just that I hadn’t had this problem before when I was launching Flye. ---
**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:** [April 18, 2026, 2:20am UTC](https://help.galaxyproject.org/t/flye-jobs-dont-start/11048/4 "2026-04-18T02:20:45Z")