Troubleshooting: Workflow Chain Experiment Execution and Pinning
Issue:
In version 2.3.3 users were able to resubmit a workflow within in a workflow chain rather than the whole workflow chain (WFC) itself
This would be done in cases where revisions are needed to be made before proceeding to the next workflow (WF)
Currently, in 3.0 it is not possible to set a "Default" pinned workflow or workflow chain version
When creating new experiments, the "Version" will default to the latest un-pinned workflow or workflow chain
Users have the option of selecting a pinned version from the "Version" drop-down list if needed
When users specify a pinned version for new experiments, the new workflow node experiments will not be compatible with old workflow node experiments in the backlog, and users will not be able to combine old and new experiments in the same sample sheet
Solution:
Users should not move the originating node as this will "break" the experiment and users would need to transition again from the node before
For example, in graph form: WF1 ----> WF2 ----> WF3
If there are issues with transitioning samples to WF3, edit the transition between WF2 to WF3
Be careful NOT to move or edit the actual WF node in any way as doing so will drop experiments currently residing in that node/WF and will need to be recovered
Example, recover experiments: navigate to sample sheet WF2 and transition again, i f WF2 was accidentally moved the user would need to go back and transition from WF1
Once completed, select SaveNOTE: The proposed solution will NOT work in the case of a pinned WFC - if a user wishes to pin their WFCs (highly recommend), users should build in points to their WFC to resubmit/go back to previous WFs to allow for the correction of mistakes