Task in Workflow stuck in ACTIVE status although it has finished with ENDED_EMPTY when modifying active Workflow

book

Article ID: 85078

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
N/A

In a running Workflow, if you add a sub-workflow which contains the script statement :STOP NOMSG in the process tab the following happens:
  • In the activities window the sub-workflow is stuck in an ACTIVE status.
  • In the statistics of the sub-workflow it indicates that it ended in a status of ENDED_EMPTY or FAULT_OTHER.
  • The master workflow gets stuck in a status of ACTIVE because the sub-workflow does not end and is also shown as ACTIVE in the activities window.
Investigation

In the following example a test workflow was edited during runtime and the PJOBP.BUGTEST.CHILD was added.

<Please see attached file for image>

0EMb0000000IVd7.png

PJOBP.BUGTEST.CHILDĀ contains :STOP NOMSG in the process tab:

<Please see attached file for image>

0EMb0000000IVdC.png

Cause

Cause type:
Defect
Root Cause: The sub-workflow does not get the correct end status.

Environment

OS Version: N/A

Resolution

Update to a fix version listed below or a newer version if available.

Fix Status: Released

Fix Version(s):
Component(s): AE Server and Initialdata

Automation Engine 12.1.0 - Available
Automation Engine 12.0.2 - Available
Automation Engine 11.2.5 - Available

Additional Information

Workaround :
Cancel the sub-workflow manually.

If the sub-workflow is added before starting the master workflow, it will result in the sub-workflow ending with an ENDED_EMPTY status and the master workflow finishes with as status of ENDED_OK.

Attachments

1558693490859000085078_sktwi1f5rjvs16m86.png get_app
1558693488827000085078_sktwi1f5rjvs16m85.png get_app