Hi @AEJ
Thanks for sending in the bug report as @wm75 suggested!
I replied to your report with the message below. In short, when a tool reports an issue with fastq data content, starting with content checks is where to start. This is how I replied to your email.
However, after taking a closer look at your most recent reruns (and QA), the reads themselves seem fine now, and I can see that different samples may fail with your exact reruns on the full collection. This was an important clue!
The jobs are likely failing for a technical issue. We had some cluster hiccups over the last week or so but this can happen at any time (thousands of jobs are processing, constantly!). Some jobs will fail by chance and produce an unreliable error message.
What to do
Try a rerun! You won’t want to rerun the entire collection. Instead, only rerun the failed job(s).
Full details with screenshots are here (including the Planemo option for bunk reruns!). → Rerunning only failed jobs in a workflow: Replace and Resume functions - #2 by jennaj