FAULT_OTHER when Maximum Runtime (MRT) stops event
Document ID :
Last Modified Date :
Show Technical Document Details
CA Automic Workload Automation
CA Automic Workload Automation:Release:11.2
CA Automic Workload Automation:Release:12.0
CA Automic Workload Automation:Release:12.1
(JSCH) contains several
(EVNT). In the example below, the same event is started several times, but that does not change the issue. The
triggers every minute in the example.
All events are stopped at the same time by Maximum Runtime (MRT). In the test case 15:10 (yellow marked above).
The screenshot above shows the statistics of the scheduler, the event started by the scheduler and the children of the event. And the details of the child-event (!EVNT).
If an event is triggered around the time the MRT stops this event, the child (!EVNT) ends with
(orange marked in the screenshot above).
The expectation is, that as long as the !EVNT was started before the MRT kicks in, it is finished normally.
An error has been fixed where events did not work properly if canceled due to the MRT. The event has been canceled but in parallel also did activate an event execution. Therefore the !EVNT did end with FAULT_OTHER.
Please install a fixed version:
AE Server and Initialdata
Automation Engine 12.2.0 - Planned release date: 2018-06-19
Automation Engine 12.1.3 - Planned release date: 2018-09-24
Automation Engine 12.0.7 - Planned release date: 2019-01-14
Automation Engine 11.2.9 - Planned release date: 2018-10-09
Was this information helpful?