Skip to content

Y26-125 - [BUG] Make re-uploading a dual index library manifest push data to MLWH iseq_flowcell table #5677

@KatyTaylor

Description

@KatyTaylor

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:

  1. 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')
  2. Make UAT Actions - Test Submission for multiplexing + sequencing (e.g. NovaseqX) on that plate barcode
  3. 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.
  4. Make changes to tag information e.g. change the tag plate/set and tag well for one of the wells.
  5. Re-upload the manifest
  6. Check tags are updated in plate
  7. Check tags are updated in downstream plates/tubes
  8. 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

Metadata

Metadata

Assignees

Labels

BugBug in codeSize: MMedium - medium effort & riskticket: generatedbugs that emerge from users creating request tickets

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions