External dependencies are not skipped if the entire workflow is skipped, instead remain in status "WAITING FOR PREDESESSOR"

Document ID : KB000087655
Last Modified Date : 14/04/2018
Show Technical Document Details
Error Message :
U00012205 Deactivation of task '' (RunID '') not possible, because there are '0000000001' active tasks inside this workflow construct remaining.

There is an incorrect Job status in the EJPP table for the following scenario:
A master-workflow contains a sub-workflow. The sub-workflow contains an external dependency. If the sub-workflow gets skipped the external dependency will remain in status 1700 "Waiting for predecessor" although it should be 1930 "Ended skipped".  As a result, the workflow cannot be deactivated in the activities window and an error message similar to the one above will be displayed.
See the example below where a master-workflow contains a sub-workflow.  The sub-workflow contains an external dependency.

The external dependency is NOT skipped and the details of the Workflow will look similar to this:

In the database, the status is incorrect as seen in the example below.
Cause type:
Root Cause: External dependencies are not skipped if a whole workflow is skipped. They remain in a "WAITING FOR PREDESESSOR" status and the workflow can not be deactivated.
This field was added on 30/03/2017. This article has not been updated yet. Refer to the "Description" or "Workaround" sections for solution information.

Fix Status: Released

Fix Version(s):
Automation Engine 11.2.3 - Available
Automation Engine 11.1.5 - Available
Automation Engine 10.0 - will not be fixed
Additional Information:
Workaround :