ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

AWA: Nested workflow is blocked but parent workflow shows as active

book

Article ID: 146006

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

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? 

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

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.