With Portal Ocicat release; in https://github.com/umccr/data-portal-apis/pull/597 we have combined wgs_alignment_qc and wts_alignment_qc into single wgts_alignment_qc trigger point in orchestration step.
Note though that wgts_alignment_qc is only a placeholder workflow type for the purpose of trigger aggregation only. We never capture this as workflow type in Portal database Workflow table.
Regression:
It works most of the part. However, the new logical placeholder type wgts_alignment_qc bugs the orchestrator batch & batch run mechanism. The placeholder workflow type is unaware of the context and, unable to re-construct from the persistent store / database record.
It effectively blocks ability to re-trigger Alignment QC step from the orchestrator batch trigger; after bcl_convert workflow step.
Context:
With Portal Ocicat release; in https://github.com/umccr/data-portal-apis/pull/597 we have combined
wgs_alignment_qcandwts_alignment_qcinto singlewgts_alignment_qctrigger point in orchestration step.Note though that
wgts_alignment_qcis only a placeholder workflow type for the purpose of trigger aggregation only. We never capture this as workflow type in Portal databaseWorkflowtable.Regression:
It works most of the part. However, the new logical placeholder type
wgts_alignment_qcbugs the orchestrator batch & batch run mechanism. The placeholder workflow type is unaware of the context and, unable to re-construct from the persistent store / database record.It effectively blocks ability to re-trigger Alignment QC step from the orchestrator batch trigger; after bcl_convert workflow step.
This does not effect to ctTSO batches.
Actions: