Mark Fleharty

1. Community
2. General Discussion
3. Workflows aborted due to exceeding quota

I'm also running into the same issue.

• View comment
• January 19, 2024 15:56
• 0 votes

1. Community
2. General Discussion
3. New error (Validation errors: Extra inputs) running somatic calling pipeline: problem with Cromwell 48?

Jason Cerrato I was able to circumvent the issue on my own.  But it's good to know the solution as well of reimporting the workflow.   Thank you!   Mark  

• View comment
• June 22, 2020 13:26
• 0 votes

1. Community
2. General Discussion
3. New error (Validation errors: Extra inputs) running somatic calling pipeline: problem with Cromwell 48?

I have a workspace, that worked months ago, but I simply tried to rerun an analysis, expecting it to call-cache, but I got this error.

• View comment
• June 20, 2020 15:50
• 0 votes

1. Community
2. Known Issues
3. Hanging Localization Step

I believe I'm having the same issue: I'm sharing this workspace with  GROUP_FireCloud-Support@firecloud.org https://app.terra.bio/#workspaces/broad-firecloud-dsde/BloodBiopsyDuplexPipeline_staging_...

• View comment
• January 27, 2020 21:39
• 0 votes

1. Community
2. General Discussion
3. Workflow error, key not found

I'm also experiencing this issue, and my workflow does NOT use Docker Hub.  I'm using GCR, and quay.io.   ** Turns out I was wrong, my workflow does reference Docker Hub in a sub workflow **

• View comment
• Edited October 16, 2019 20:57
• 1 vote

1. Community
2. Active Feature Requests
3. Check illegal set names when selecting data in "Select samples to process"

Great, thanks @sushma.  

• View comment
• October 15, 2019 15:38
• 0 votes

Check illegal set names when selecting data in "Select samples to process"

In the "Select Data" box, also titled "Select samples to process" it allows you to change the name of the set you create in, "Selected rows will be saved as a new set named".   If you give it an il...

• Mark Fleharty
• October 11, 2019 20:09
• 2 followers
• 2 comments
• 0 votes

1. Community
2. Completed Feature Requests
3. json file currently deoesn't include "optional" arguments

Sushma,   Great, thanks!   Mark  

• View comment
• July 29, 2019 17:24
• 0 votes

json file currently deoesn't include "optional" arguments

Hello,   When looking at the Workflows tab, under INPUTS.   You can download a json file, but if there are optional arguments, they don't appear to show up in the json file, even if show hidden is ...

• Mark Fleharty
• July 26, 2019 18:59
• 2 followers
• 3 comments
• 0 votes
• Completed