Force canceling executions should actually kill the workflow process

Description

Right now, when an execution is cancelled (or force cancelled) if the underlying subprocess running the workflow task is stuck (eg sleep(99999)), or if the workflow was manually written, and does not rely on the tasks graph for execution (which means it's not checking for the execution status), then this process might continue living. The proposal here is to kill it on those situations.

Status

Assignee

Łukasz Maksymczuk

Reporter

Pavel Brodsky

Labels

None

Target Version

4.4

QA Owner

Uri Wygodny

Premium Only

no

Documentation Required

Yes

Why Blocked?

None

Release Notes

yes

Priority

None

Sprint

None

Priority

Unprioritized
Configure