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.

Child Event goes to FAULT_OTHER status after Maximum runtime exceeded


Article ID: 85112


Updated On:


CA Automic Workload Automation - Automation Engine


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.


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 type:
By design
Root Cause: Status is appropriate.


OS Version: N/A


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):

Additional Information

Workaround :