You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Portal Ocicat release; in #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.
This does not effect to ctTSO batches.
Actions:
Investigate and fix it
The text was updated successfully, but these errors were encountered:
Context:
With Portal Ocicat release; in #597 we have combined
wgs_alignment_qc
andwts_alignment_qc
into singlewgts_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 databaseWorkflow
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.
This does not effect to ctTSO batches.
Actions:
The text was updated successfully, but these errors were encountered: