I've got a workflow that uses the old samtools mpileup (v0.0.1) on the main galaxy instance. The next step has been stalling due to metadata not being autodetected in the subsequent dataset. It seems to be happening regardless of the input .bam file. Is this a problem with galaxy? The workflow has worked in the past, probably last time about a month ago.