Unable to export workflow to workspace Completed
I am unable to export a workflow to a workspace. I receive the error:
Error: Substream Source(EntitySource) cannot be materialized more than once
I tried with both an existing workspace and a new workspace. The workflow I want to export resides in the Broad workflow repo. It's URL is: https://portal.firecloud.org/?return=terra#methods/getzlab/CGA_HG38_WES_Characterization_v0.5_Dec2020/1
-Chet
Comments
10 comments
Hey Chet Birger,
Just wanted to let you know that our engineers have found the root cause and resolved the error Substream Source(EntitySource) cannot be materialized more than once. Thanks again for reporting this!
Kind regards,
Jason
Hey Chet,
Thanks for writing in. This appears to be a known error with trying to export a workflow in FireCloud under certain circumstances. Can you share your method configuration and workspace with our engineer mbemis@broadinstitute.org for further investigation?
Kind regards,
Jason
A colleague pointed this out to me. She said that if I repeatedly attempt to export the workflow to a workspace, eventually it would work. It was successful on the 22nd try.
This is a real pain though and needs a real fix. I will share workflow with Matt....he can try exporting it into any workspace.
-Chet
Hi Chet,
Thank you for sharing that. Our engineers are interested in getting to the bottom of why this happens. If you or your colleagues continue running into this, please let us know and share the method config/workspace with Matt so that he has more data points to work with.
I will let Matt know the workflow has been shared.
Kind regards,
Jason
Hi Chet,
Our engineers believe they have identified the underlying issue and a potential fix. I'll be happy to let you know when the fix is in place.
In the meantime, please feel free to copy the workflow to other workspaces using the Terra UI if needed.
Kind regards,
Jason
Thanks Jason. Yes, please let me know when the fix is in place.
Regards,
Chet
Hi Chet,
Happy to do so. The team investigating have let me know that it will require more time to investigate and work on a fix, but I'll be happy to let you know once I receive the word that it's been resolved.
Kind regards,
Jason
Is the fix deployed? If so, when did it get deployed?
-Chet
Hi Chet,
The fix was deployed approximately 30-60 minutes ago.
Kind regards,
Jason
thanks!
-Chet
Please sign in to leave a comment.