Schedule object tasks going to ENDED_TIMEOUT when starting at 0:00 GMT

book

Article ID: 211862

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

With a JSCH that has tasks that execute at 0:00 GMT (or a different defined period turnaround), sometimes those tasks go into ENDED_TIMEOUT start time exceeded instead of activating as expected.

Cause

Timing issue due to system load. 

Environment

Release : 12.3

Component : AUTOMATION ENGINE

Resolution

During period turnaround, if the system is very busy, it can be that other turnaround tasks occur and, by the time processing reaches the scheduled task, the system time has moved on causing the check to register as ENDED_TIMEOUT.

Our recommendation would be to make sure the defined period turnaround does not correspond to activation of tasks within the schedule. This can be done either by changing the turnaround of the task or the scheduled times of activation.