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.
An Automic Workflow stays in waiting for external dependency even if the external dependency task already executed.
Article ID: 103835
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Broadcom Support does not recommend to use an external dependency that depends on a task within the same workflow, as shown in the screenshot below: the task which has an external dependency, will need to be manually skipped.
Environment
Products: Automic Automation Engine v10, v11,v12
Operating System: All
Resolution
Please use one of the option below:
Option 1: Use a Pre-Condition on the first task of the workflow as shown below. The task that is expected or required must be executed outside the workflow.
Option 2: Use an external dependency of a task outside the workflow.
Option 3: create a sub-workflow with the flag creation JOBS disconnected inside it, that way the main workflow will finish as soon as the sub-workflow starts.
Attachments
Feedback
Yes
No
Powered by
