Be sure to mark history objects as accessible when creating the link by clicking on the small checkbox next to the “Share by link” button. You can unshare and re-share if this history was already shared but the objects/datasets were not. The mailing galaxy-bugs list is private to the usegalaxy.org server admins and your data will not be exposed publically.
The original intent was to send the share link in an email to the galaxy-bugs mailing list, not to share it directly as one would with another user on the server.
I’ve got the link now. If you want to keep your history private, you can edit your post here to remove it. Anyone will be able to see it when posted here publically. It would have remained private if sent via email to the mailing list.
More feedback about the reasons why the workflow extraction failed once we review.
Hi - We are still reviewing to find out exactly why there is a workflow extraction problem with this history.
However, it appears that the datasets in the history were moved/combined from other analysis histories. This is likely a factor leading to the workflow extraction problem. When test extracting a workflow in the current history, I can get as far as including all steps up until the trimmomatic job (and excluding the rest). Excluding the trimmomatic job is not enough, and would leave out that step in your workflow anyway.
Try running the analysis in a single history, leaving contiguous jobs/steps/datasets active, then extracting a workflow.
I have been getting the same error for Microbial de novo Assembly for Illumina Data tutorial conducted by melbourne bioinformatics research group.
here I attached a screen shot of the error occured
If you are working at Galaxy Main https://usegalaxy.org, I can let you know that there were some issues with one of our web hosts earlier for a short time window. We believe that is now resolved. Please try to extract the workflow from the history again now.
Galaxy AU https://usegalaxy.org.au has not had any problems over the last few days, should you be working there instead.
If the workflow extraction fails again, could you try to attach it again or explain what your problem is with more details? Also, please note the URL of the server you are working at. The original screenshot did not attach correctly.
Thanks!
Update: I was able to fix your attachment. Try the extraction again and if it fails, what server are you working at?
