Update 9-25-2018 4pm EST
This issue is now fixed.
These jobs can be run without setting the Job Resources parameter (Galaxy chooses the cluster with available resources) or you can target one of the other clusters. Each cluster has a different profile (memory/walltime) -- Details: https://galaxyproject.org/main/
Avoid the development clusters or errors may come up unexpectedly. We really do use these for testing and no bug reports need to be sent in for odd job results when using them.
Note: There was another issue that triggered certain jobs to fail for not finding built-in indexes. This was also corrected and the specific error message can vary by tool. And there is one more issue that related to data input types that has been fixed but not applied to the server yet. This error message can also vary by the tool and does not impact all runs -- so try rerunning a few times to achieve a successful result (FastQC was one of the impacted tools).
Main point: If you had any odd job failures over the last few days, please rerun now. If the job fails, it can be sent in as a bug report or you can double check your inputs using the FAQ help here first: https://galaxyproject.org/support/tool-error/
Thanks to all for reporting the problems and for your patience while we corrected the problem.
Jen & the Galaxy team