AWA: Nested workflow is blocked but parent workflow shows as active
Article ID: 146006
CA Automic Workload Automation - Automation Engine
When executing a workflow that is nested multiple layers, the parent workflow will show as active, but the child workflow is blocked. How do you make sure the parent workflow shows the correct status?
Release : 12.3
Component : AUTOMATION ENGINE
All levels would have to have 'Block and send Abort signal to parent' selected on the dependencies tab of the workflow editor. Additionally, in Postconditions, make sure there is no "FINALLY block" as this propagates only to one level above.