Describe the bug
Re-uploading a dual index library manifest (plate_dual_index_tag_library in manifest_types.yml) with new tag information does not successfully push changes to the MLWH iseq_flowcell table. It does work with other library manifest types.
See investigation and suggested approaches here - #5604 (comment)
FreshSerivce/RT Ticket Number
SR-56929
To Reproduce
Steps to reproduce the behaviour in UAT environment:
- Generate and upload dual index library manifest (studies -> pick a study -> create sample manifest -> create manifest for library plate -> template 'Library plate - dual index tag plate, purpose 'Library Stock Plate')
- Make UAT Actions - Test Submission for multiplexing + sequencing (e.g. NovaseqX) on that plate barcode
- Click through Limber multiplexing pipeline, LabWhere Reception postmanpat, SS sequencing pipeline - when sequencing batch is released, it should appear in the mlwhd_mlwarehouse iseq_flowcell table.
- Make changes to tag information e.g. change the tag plate/set and tag well for one of the wells.
- Re-upload the manifest
- Check tags are updated in plate
- Check tags are updated in downstream plates/tubes
- Check tags are updated in mlwhd_mlwarehouse iseq_flowcell table --> this is where it fails
Expected behaviour
Tags are updated in mlwhd_mlwarehouse iseq_flowcell table
Describe the bug
Re-uploading a dual index library manifest (
plate_dual_index_tag_libraryin manifest_types.yml) with new tag information does not successfully push changes to the MLWH iseq_flowcell table. It does work with other library manifest types.See investigation and suggested approaches here - #5604 (comment)
FreshSerivce/RT Ticket Number
SR-56929
To Reproduce
Steps to reproduce the behaviour in UAT environment:
Expected behaviour
Tags are updated in mlwhd_mlwarehouse iseq_flowcell table