I noticed in a recent job:
https://portal.firecloud.org/#workspaces/broad-firecloud-dsde/LiquidBiopsyPipeline_NormalNormalExperiment/monitor/3f4b3628-56d2-414e-9a17-615f29882842/ec1a8dd4-2f92-41ec-ac20-3e7c508a789e
I can't access the data by clicking the link:
GenerateDuplexConsensusBams.ClipBam
under the Calls section.
It gives me the following link, which has nothing there...
https://console.cloud.google.com/storage/browser/fc-secure-76779bb4-8406-4b32-b100-b5c84daf3cf9/3f4b3628-56d2-414e-9a17-615f29882842/GenerateDuplexConsensusCalls/ec1a8dd4-2f92-41ec-ac20-3e7c508a789e/call-GenerateDuplexConsensusBamsTumor/GenerateDuplexConsensusBams/1bc82f0f-5def-4ed7-9df9-d9312ac8f645/call-ClipBam?pli=1
I believe the correct link should be:
https://console.cloud.google.com/storage/browser/fc-secure-76779bb4-8406-4b32-b100-b5c84daf3cf9/3f4b3628-56d2-414e-9a17-615f29882842/GenerateDuplexConsensusCalls/ec1a8dd4-2f92-41ec-ac20-3e7c508a789e/call-GenerateDuplexConsensusBamsTumor/GenerateDuplexConsensusBams.GenerateDuplexConsensusBams/1bc82f0f-5def-4ed7-9df9-d9312ac8f645/?pli=1
It appears that the link for the call is not constructed correctly when dealing with sub-workflows.
Thanks,
Mark