Have you tried this more than once? It is possible one of the servers was just busy. How large was the data? Is it in a collection or an individual dataset?
You can double-check that the format is actually
fastqsanger by redetecting the datatype. Use the pencil icon to reach: Edit attributes > Datatype > use the button to “detect datatype”. If you do not get
fastqsanger as the result there is a content or format problem that makes the data out-of-specification. Some of these tools also process
fasta data – and if the data is in that format, the correct datatype should be assigned.
Yes, the queue is quite long for jobs that run on the cluster that processes
Unicyler. The same is true for
RNA-Star. Confirm that the inputs are Ok, and if they are, then allow any queued jobs to stay queued to ensure the fastest processing. If you delete and rerun, that will place the new jobs back at the end of the queue again, extending wait time. If the inputs are problematic – fix as needed, then go ahead and rerun.
Confirming your inputs are Ok can help here too. Also, make sure you are using the most current version of the tool (and all tools). A job failing so quickly is a strong indicator of an input problem. If the inputs are Ok, then you can submit a bug report. Putting some details into the comments would help – including a link to this Galaxy Help topic for context. Or @wm75 may ask for something different (he is an admin for the EU server).
The usegalaxy.eu server automatically reruns jobs that fail – and that is what the message/blue box is notifying you about. This helps to eliminate transient cluster/server-side issues (rare, but happen!). A rerun for any odd failure is a good idea. Not all public Galaxy servers do this automatically – but you can rerun yourself.