Abort Task used in Workflows produces ENDED_JP_ABEND that breaks the Dependencies

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

You are working with a Worfklow (JOBP) and notice that the Dependencies are not respected anymore and other  tasks get the status ENDED_JP_ABEND  as soon as one task receives the status ENDED_JP_ABEND due to the fact that you have set "If status or Latest Time mismatches"  Abort task

On the example below, see the Dependencies on JU.FAB.BATCH11 where  Abort task was used 

When we execute this JOBP we obtain the following results:

You would have expected that the logic would have been respected and the JU.FAB.CRITICAL would have been executed as the JU.FAB.BATCH12 completed in ENDED_OK, but instead the whole workflow is set to ENDED_NOT_OK - aborted and the JU.FAB.CRITICAL is instead of being executed is set to ENDED_JP_ABEND.

The same occurs with a different test where ANY_ABEND is used and this status ENDED_JP_ABEND is not considered as the whole workflow execution is interrupted.

 

 

Environment

Automic Automation all versions

Cause

The issue stems from the use of the "Abort Task" option in the task dependencies.

• Logic: In Automic Workload Automation, when a task dependency is set to Abort, it does not just cancel that specific task; it cancels the entire Workflow (JOBP).
• Result: Once the Workflow container itself is set to an "Aborted" status (ENDED_JP_ABEND), the engine stops processing further tasks within that container. This overrides any logic in following tasks because the parent container is no longer active. ENDED_JP_ABEND stands for JP (Job Plan = Workflow)  and ABEND means abnormal end, so if a workflow is abended nothing else must be started anymore  as the container (parent = workflow ) is set to ABEND.

Resolution

To achieve the desired behavior where the workflow continues even if a job fails, you must change the dependency action:

1. Open the Workflow and select the properties of the task (e.g., JU.FAB.BATCH11).
2. Go to the Dependencies tab.
3. Change the "Else" action from Abort Task to Skip Task.

Why this works: Using Skip Task allows the individual task to fail/skip without propagating an "Abort" signal to the entire Workflow. This keeps the Workflow container active, allowing the engine to evaluate the conditions for JU.FAB.CRITICAL (such as your OR condition) and execute it as expected.

Example of the expected output when Skip task is used:

Additional Information

Dependencies documentation available here