2.1 years ago by
The server http://usegalaxy.org is most likely just busy or you had many jobs associated with your account queued. That said, this long of a wait is unusual. If something more is going on server-side - we will write back with an update.
Please know that other issues can be a factor. Inputs (incorrect format, empty inputs, metadata issues), custom reference genome formatting, many compute intensive jobs queued .. these usually result in job failures or unexpected results. Should job delays continue and you can't find the source of the problem or simply want feedback, please feel free to send in a bug report. Include a link to this post in the comments. We'll check the entire history, not just the specific problem reported. Make sure the data to be examined is undeleted. Or, you can use the self-help troubleshooting list linked below that covers the basic checks - these are the same checks we do here for reported problems.
Thanks for reporting the issue. Different jobs are sent to different clusters. This is probably why other jobs started while the Cufflinks jobs were still in queue (these are dispatched to a busier cluster). I suggest allowing these to run, even if it takes a few days. If that advice changes, will include help in the updated reply (should server issues or longer-than-normal queues are present right now).
If you are not using http://usegalaxy.org, reply with details: Local or cloud Galaxy? Some other public server (URL)? Private Galaxy? (For the last two - contacting the admins of that instance is the path toward finding out what is going on.
Best, Jen, Galaxy team