Run Inclusive Gateway test on feature-126 branch, w/out teardown and look at properties of master process. You will see wf:status is still INPROGRESS ( benign, but untidy ). Sort it out.
<wf:branches xmlns:wf="http://marklogic.com/workflow">
wf:fork2018-03-02T16:05:30.9492406Z066ab6ff-99a1-4ccb-b66f-efa20232f2ad</wf:fork>
wf:rendezvous-methodALL</wf:rendezvous-method>
wf:statusINPROGRESS</wf:status>
wf:branch-status
wf:branchInclusiveGatewayTest-01__1__0/UserTask_1</wf:branch>
wf:pipelineInclusiveGatewayTest-01__1__0</wf:pipeline>
wf:statusCOMPLETE</wf:status>
</wf:branch-status>
</wf:branches>
Run Inclusive Gateway test on feature-126 branch, w/out teardown and look at properties of master process. You will see wf:status is still INPROGRESS ( benign, but untidy ). Sort it out.
<wf:branches xmlns:wf="http://marklogic.com/workflow">
wf:fork2018-03-02T16:05:30.9492406Z066ab6ff-99a1-4ccb-b66f-efa20232f2ad</wf:fork>
wf:rendezvous-methodALL</wf:rendezvous-method>
wf:statusINPROGRESS</wf:status>
wf:branch-status
wf:branchInclusiveGatewayTest-01__1__0/UserTask_1</wf:branch>
wf:pipelineInclusiveGatewayTest-01__1__0</wf:pipeline>
wf:statusCOMPLETE</wf:status>
</wf:branch-status>
</wf:branches>