Open istvankleijn opened 4 months ago
Hi @istvankleijn, this is not intentional - I'll check in with our platform team for advice.
@SamStudio8 Some more details on this: It does not seem to be a wf-basecalling issue because I am having a similar problem with wf-human-variation. I updated wf-basecalling from 1.2.2 to 1.3.0 and can only select 1.3.0, master, and prerelease, and I updated wf-human-variation from 2.2.4 to 2.2.6 and can select 2.2.5, 2.2.6, master, and prerelease. So it appears that I cannot switch to any revision prior or equal to the version that was installed previously after I apply a workflow update.
My workaround for anyone else running into this: I downloaded the workflow source code at the release tag I wanted and extracted that to epi2me/workflows/epi2me-labs
folder. That seems to work as expected.
Operating System
Other Linux (please specify below)
Other Linux
Ubuntu 20.04.4
Workflow Version
v1.2.2
Workflow Execution
EPI2ME Desktop (Local)
Other workflow execution
No response
EPI2ME Version
V5.1.14
CLI command run
No response
Workflow Execution - CLI Execution Profile
None
What happened?
Not sure if this is a workflow bug or in the desktop GUI, but I cannot seem to downgrade to any version of the workflow prior to v1.1.9. I updated to v1.2.2 for one project but ran into a dorado bug so would like to return to v1.1.7 which I was on for another project. Is this intentional? I can probably attempt to get around this with the command line interface but would prefer to reproduce my earlier setup.
Relevant log output
Application activity log entry
No response
Were you able to successfully run the latest version of the workflow with the demo data?
yes
Other demo data information
No response