If you are running the work at a public Galaxy server, the queue times for larger compute-intensive tools are usually a bit longer than for simpler tools.
The best strategy is to queue jobs up and allow those to fully process. If you delete and rerun, that will place the new job back at the end of the queue again, further extending wait time. The only reason to rerun is if you already know there is a problem with the inputs that will likely lead to a job failure (or results you don't want).
For urgent or time-sensitive work, or if you'd just like to have more quota space and not compete with others for common public resources, consider setting up your own Galaxy server. The GVL version of Cloudman is a popular choice but there are many others. Please see: https://galaxyproject.org/use/
On Mon, Aug 3, 2020 at 10:47 AM Xiaoshen Zhang email@example.com wrote:
Dear Galaxy team,
Recently, I have been running TRINITY for RNA-seq data analysis, but the “my history” status always display the job is waiting to be run (the color never changed). When I implemented some analyses on galaxy, ONLY this method displayed “job waiting to be run” and nothing happened.
After trying for several times and everything, I suppose something wrong with my account or the TRINITY method.
Hope you can kindly fix this problem. Thanks for all the efforts you have been made. My account is exactly this email address. Details for TRINITY: ( https://usegalaxy.org/root?tool_id=toolshed.g2.bx.psu.edu/repos/iuc/trinity/... )