We observed this in a benchmarking run of the best practice QC workflow on 1000 BRCA tumor/normal pairs. Of the 1000 workflows, 991 succeeded, 5 failed, and 4 are still flagged as running. This is an issue with two of the workflows that are reported as running. In each case, the workflow is reported as running, but if you look at call-level data for the workflow, there is none. In fact, the bucket folder associated with the workflow was never created.
The workspace in which we see this is broad-firecloud-broade/BenchmarkWorkspace_template_CloneTestSharing2; this is a controlled access workspace.
The analysis submission in which this stalled workflow was launched is 7afeacc4-d787-4ca6-8e32-7acab85c1d1f
The two pair id's whose workflows are stalled at the start are:
BRCA-A7-A3J1-TP-NB
BRCA-BH-A0B0-TP-NB