Downstream jobs finishing first


I’m doing some basic de novo transcriptome analysis and have found that while I’m assembling transcripts in Stringtie, my downstream jobs such as running stringtiemerge, gffcompare, and featurecounts all finished even though I still had some original Stringtie jobs going…

And then DESeq2 fails to run. This doesn’t seem right, or even possible. Does anyone have any insight on this?

That should not happen, can you maybe share a history with us in which this happens?

I have never seen this before.

1 Like

Unfortunately I ended up removing those datasets and starting over (I was running out of space). Since that attempt, I’ve just been running jobs in batch mode one at a time to avoid this issue. I will update this thread if this issue occurs again.

Related Q&A Stringtie not running

It seems that the problem was some setting in the workflow used.

1 Like