Error if you use CHECK HISTORY in a postcondition after another condition that evaluates to FALSE

book

Article ID: 87738

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
U0020411 The command 'EXIT' in ' XC_INC.CONDITION.CHECK_HISTORY ', line '00036' stopped the generation of this task.

if CHECK HISTORY is used in a post condition after another condition that evaluates to FALSE, you receive the above error. In the example below, if CHECK CONNECTION gives false as theĀ 
<value> connection is down, the error will appear.

<Please see attached file for image>

0EMb0000000PqBb.png

Cause

Cause type:
Defect
Root Cause: The condition CHECK_HISTORY does not reset the error number. If more than 1 CHECK_HISTORY conditions are used in one Condition-Set and the first condition results in an error, every other following CHECK_HISTORY will result in the same error.

Environment

Release: AUTWAB99000-10.0-Automic Workload Automation-Base Edition
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 Version(s):
Automation.Engine 10.0.7 of Automation.Engine - already available

Additional Information

Workaround :
N/A

Attachments

1558692874233000087738_sktwi1f5rjvs16lvu.png get_app