13 months ago by
United States
Hello,
This has come up before for a few older workflows at Galaxy Main https://usegalaxy.org and we are still not sure of the underlying cause (the discussion was around the workflow's metadata, but never solved as far as I know). But we do have a workaround:
- Open the workflow in the workflow editor. If it in a shared state, import it into your Saved Workflows first.
- In the editor, use the function to "Save As" and give it a new name.
- Use that newly saved version. For others, this resolved the problems.
Let us know how that goes! Thanks, Jen, Galaxy team
Was this at usegalaxy.org? When was the last time you ran it successfully?
yes. it was at usegalaxy.org. I ran it 2 month before and it was woking.