Hi @Niamh
Thanks for letting us know which server you are working at: Galaxy Main https://usegalaxy.org.
There were some busier server days over the last few weeks but it doesn’t seem like that is your issue. Instead, the problem is most likely with the inputs (format or content).
- https://usegalaxy.org/ -- Server issues Feb 25, 2020 Resolved
- My job ended with an error. What can I do? >> https://galaxyproject.org/support/tool-error/#type-execution-exceeds-maximum-allowed-job-run-time-walltime
Resolving input issues
There are three core inputs to this tool. Each is described in the tool form. It is very important that the format of each matches the examples. In particular, the first column (gene identifier) must be in the same format for all three of the inputs.
Meaning, if any contain extra content, such as a trailing .N after the gene name (where N is a number, specifically the version), the “dot” and “version-number” should be either present in all inputs, or better in most cases, removed from all inputs.
Please give this a review in your particular data. If all seems correct, then allow the job to fully process. If any are a mismatch, make corrections and rerun. If the job still ends with another error once the inputs seem OK, three options:
- Post back a few lines (2-3) from each of the three inputs. Please try to preserve formatting by quoting the text.
- Generate a share link to the history and post that back. Make sure that all inputs and outputs are in an undeleted state, and that “objects” in the history are shared.
- Send in a bug report from one of the failed datasets (“bug icon” in the red error dataset), then post back that you sent one in so we know when to look for it. Be sure to include a link to this Galaxy Help post in the comments so we can find it quickly and associate it with your question here.. If you already sent one in, go ahead and send it in again with the link, then let us know.
For any choice, you can post the information publically in this thread or post back to our direct message thread. Either is fine, it just depends on your comfort level with making a portion or all of your data public (for expanded community help with troubleshooting).
If you choose to keep this private, we won’t post anything back public that is private, just summarize the usage issue and how to address it, in general terms, IF it will help others. This tool and the tutorial that includes it do not have any current known issues - but if one is uncovered, we can ticket/address that with anonymous data as well.
Let’s start there. Thanks!