Bug #3136

Updated by Tom Clegg over 9 years ago

Steps to reproduce: 

 # Run a pipeline 
 # Hit "Stop".    This doesn't actually cancel the running jobs, see Bug #3165 
 # Go to the individual job page and cancel the job. 
 # Since the arv-run-pipeline-instance is no longer updating the copy of the job information in the pipeline instance record (why should it, it's stopped, right?) the pipeline will continue to show the job as running. 

 Quick resolution: 

 * In Workbench, look up each job by UUID instead of rendering the copy of the job record stored in the pipeline instance.