Child Event goes to FAULT_OTHER status after Maximum runtime exceeded

book

Article ID: 85112

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine AUTOMIC WORKLOAD AUTOMATION

Issue/Introduction

Error Message :
U00010013 Activation of '' was aborted by user.

Child Events (!EVNT) go into a status of “Fault_Other” when a Maximum runtime (MRT) is defined.  Before the MRT is exceeded the !EVNT is generated and aborts with the above error message.

Investigation

When executing a simple Time Event (Wait 40) with the Event already generated (running as a Child Event), and either the MRT of the Event has exceeded or the user quits the Event, the Child Event finishes but ends with a status of  Fault_Other – Start impossible. Other error. 

In the details view of the Child Event the last message contains:

 
 U00010013 Activation of '<TIMEEVENT>' was aborted by user.

Cause

Cause type:
By design
Root Cause: Status is appropriate.

Environment

OS Version: N/A

Resolution

The status is valid due to the fact that the Time Event was aborted as the MRT ran out time, so it was in essence aborted by the user who started the event.

Fix Status: No Fix

Fix Version(s):
N/A

Additional Information

Workaround :
N/A