Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Some aborted workflows still have "running" subworkflows

See original GitHub issue

A few workflows that we aborted in Cromwell-as-a-Service have the status “Aborted” (e.g. “429e0aaf-c429-4438-a12d-734f1f444801”) but the subworkflow that was running when the parent workflow was aborted is still in the “running” status. When trying to abort the subworkflow that is still running (“34074359-f8ed-4402-ba65-c92ab550e999”), I see the error:

{
  "status": "error",
  "message": "Couldn't abort 34074359-f8ed-4402-ba65-c92ab550e999 because no workflow with that ID is in progress"
}

It looks like Cromwell thinks the workflow is not running, but it’s metadata says that it is.

Issue Analytics

State:
Created 5 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

gemmalamcommented, May 24, 2019

Thank you @samanehsan I am going to close this for now and we can re-open if necessary. This ticket has been moved to our new Jira board, too 😃 https://broadworkbench.atlassian.net/browse/BA-3654

0reactions

samanehsancommented, May 21, 2019

I haven’t seen this show up again recently @ruchim