Modify Workflow at runtime -> New Task with dependency Status ANY_OK does not start if parent task has ended with Status ENDED_OK
Article ID: 87844
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
When modifying a Workflow at runtime and adding a new task with the dependency status ANY_OK, if the previous task has already finished with ENDED_OK, the added task will never start.
N/A
When modifying a Workflow at runtime and adding a new task with the dependency status ANY_OK, if the previous task has already finished with ENDED_OK, the added task will never start.
Environment
Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition
Component:
Component:
Cause
Cause type:
Defect
Root Cause: Adding a dependency did not work with MODIFY_TASK, if the source task of the dependency has already ended. ADD_DEPENDENCY added an additional predecessor even the task has already ended and after committing the changes, the task would wait forever.
Defect
Root Cause: Adding a dependency did not work with MODIFY_TASK, if the source task of the dependency has already ended. ADD_DEPENDENCY added an additional predecessor even the task has already ended and after committing the changes, the task would wait forever.
Resolution
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.2 – Available
Automation Engine 11.1.4 – Available
Fix Status: Released
Fix Version(s):
Automation Engine 11.2.2 – Available
Automation Engine 11.1.4 – Available
Additional Information
Workaround :
Do not add a Dependency status in the added task.
Do not add a Dependency status in the added task.
Feedback
Yes
No
Powered by
