# Job waiting to run, but others are working?

**URL:** <https://help.galaxyproject.org/t/job-waiting-to-run-but-others-are-working/12431>\
**Category:** usegalaxy.org support\
**Tags:** queued-gray-datasets\
**Created:** [May 7, 2024, 8:38pm UTC](https://help.galaxyproject.org/t/job-waiting-to-run-but-others-are-working/12431 "2024-05-07T20:38:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ebrandt](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/ebrandt/32/5558_2.png) [@ebrandt](https://help.galaxyproject.org/u/ebrandt)\
**Post date:** [May 7, 2024, 8:38pm UTC](https://help.galaxyproject.org/t/job-waiting-to-run-but-others-are-working/12431/1 "2024-05-07T20:38:33Z")

</div>

Hello, I am new-ish to Galaxy. I’m trying to run a smaller job - just Join two Datasets on a normalized count file with a list of significant genes file - and it’s stuck in Waiting to run. I tried re running the job several times, but it’s still stuck. I gave up on it and started some other jobs for a different analysis in the same history, and those are starting and finishing fine. Generally I would just wait, but it seems odd to be stuck on a smaller job but be able to do larger jobs. Is there something wrong with the job I’m trying to do? I’m just at this tutorial step [https://training.galaxyproject.org/training-material/topics/transcriptomics/tutorials/ref-based/tutorial.html#hands-on-extract-the-normalized-counts-of-the-most-differentially-expressed-genes](https://training.galaxyproject.org/training-material/topics/transcriptomics/tutorials/ref-based/tutorial.html#hands-on-extract-the-normalized-counts-of-the-most-differentially-expressed-genes) using my own data.

---

<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:** [May 7, 2024, 9:00pm UTC](https://help.galaxyproject.org/t/job-waiting-to-run-but-others-are-working/12431/2 "2024-05-07T21:00:24Z")

</div>

Welcome, @ebrandt

Different types of tools get routed to different clusters, and which cluster happens to be free for new jobs changes all the time. So, what is going on seems normal.

And remember, every time you delete and rerun a job, that new jobs is added back to the end of the queue again. If you do this often enough, a job may never get the chance to move up and actually run. So, try to leave queued jobs queued.

Later on, you can use a workflow. Or, you could use one now since each tutorial includes a workflow template. 🙂 Using a workflow queues all of your jobs at once!

More details

> [@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) 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).

Hope this helps!