Hello Sheena, Started jobs will be in the queue - it is important to not stop and restart. You want to leave them in the grey state while they wait their turn to run. Galaxy has been under a very high NGS tool load for about a week, and even though we have substantial resources dedicated to supporting analysis on the public server, this has led to progressively longer delays. Everyone has to wait when running jobs on the public instance (even the Galaxy team!). We are closely monitoring the recent surge in activity to ensure that everyone has fair access on the main public instance. If you or anyone reading this post is in a rush, a cloud instance would be recommended: http://usegalaxy.org/cloud Thanks for asking - checking in is always OK, Best, Jen Galaxy team ps: This is the same message I've been sending to everyone reporting the same issue, so apologies to the list subscribers for the repeats. On 4/25/12 1:01 PM, Scroggins, Sheena wrote:

Hi,

My cufflinks jobs sat in the queued state for 12+ hours so I restarted them this morning. They've been in the queued state now for about 2-3 hours. Any idea why?

Here's a link to my history:

https://main.g2.bx.psu.edu/u/sheenams/h/clone-of-s1jaf13mir-active-items-onl...

Thanks

Sheena

__________________________________________________ Sheena Scroggins Post Masters Research Associate-Bioinformatics Pacific Northwest National Laboratory

___________________________________________________________ The Galaxy User list should be used for the discussion of Galaxy analysis and other features on the public server at usegalaxy.org. Please keep all replies on the list by using "reply all" in your mail client. For discussion of local Galaxy instances and the Galaxy source code, please use the Galaxy Development list:

http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists, please use the interface at:

http://lists.bx.psu.edu/

-- Jennifer Jackson http://galaxyproject.org