We do not need to set the runocrWF variable in Argo. This is only used in the end-accession robot to decide if the ocrWF is to be created, but in Argo, we are creating the workflow on demand. Adding the variable is incorrectly causing ocrWF to be run twice.
Why was this change made?
We do not need to set the
runocrWF
variable in Argo. This is only used in the end-accession robot to decide if the ocrWF is to be created, but in Argo, we are creating the workflow on demand. Adding the variable is incorrectly causing ocrWF to be run twice.HOLD pending test on stageHow was this change tested?
Stage