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.
Some Actions not blocked when a Sub-Job ends "NOT OK"
Article ID: 87536
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Error Message :
N/A
The following action:
PACKAGES/PCK.AUTOMIC_FILESYSTEM/ACTIONS/FILE/FILESYSTEM/PCK.AUTOMIC_FILESYSTEM.PUB.ACTION.SNAPSHOT_CREATE
will not block when [email protected] (or WINDOWS) fails because the end-object of that JOBP has its dependencies set to "All states must match" to "" (nothing at all). See screenshot below.
Expected: This workflow should be blocked when the Sub-Job fails.
N/A
The following action:
PACKAGES/PCK.AUTOMIC_FILESYSTEM/ACTIONS/FILE/FILESYSTEM/PCK.AUTOMIC_FILESYSTEM.PUB.ACTION.SNAPSHOT_CREATE
will not block when [email protected] (or WINDOWS) fails because the end-object of that JOBP has its dependencies set to "All states must match" to "" (nothing at all). See screenshot below.
<Please see attached file for image>
Expected: This workflow should be blocked when the Sub-Job fails.
Cause
Cause type:
Defect
Root Cause: "End" object of workflow PCK.AUTOMIC_BOND.PUB.ACTION.SET_ENVIRONMENT_GUID has its dependencies set "All states must match" to "ANY_OK"
Defect
Root Cause: "End" object of workflow PCK.AUTOMIC_BOND.PUB.ACTION.SET_ENVIRONMENT_GUID has its dependencies set "All states must match" to "ANY_OK"
Environment
Release: WAASER99000-1.0-Automic Workload Automation-Services
Component:
Component:
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):
Package.Filesystem 1.2.1 - Available
Fix Status: Released
Fix Version(s):
Package.Filesystem 1.2.1 - Available
Additional Information
Workaround :
N/A
N/A
Attachments
Feedback
Yes
No
Powered by
