search cancel

C_PERIOD with setting 'after the previous execution ends plus', stops executing occasionally


Article ID: 242760


Updated On:


CA Automic Workload Automation - Automation Engine


An issue was found where a task with periodical execution (C_PERIOD) would stop executing for no obvious reasons. Only C_PERIODS with the setting  'after the previous execution ends plus' are affected.


Release : 12.3.x and 21.x



After the sleeping time for the C_PERIOD has passed, another 'cycle' should begin.
During the processing of the TIMER at that moment, there are 2 messages generated, the Execution of the task and the CHPRDLOG.
The problem only happens when CHPRDLOG starts after the Task in the C_PERIOD container is started (child job is still running).

When the Job starts, the EH_NextCheck is set to NULL. (the next execution time is unknown, must be calculated after the job finishes + the delay)
When CHPRDLOG starts during such a moment, the CHPRDLOG copies the EH entry with the new runid and EH_NextCheck set to null.

This causes that no further executions happen after the new start of the task - this is the actual bug.


The only workaround is to restart the C_PERIOD container for the day.



Update to a fix version listed below when they are available or a newer version if available.

Fix version:
Component(s): Automation Engine

Automation.Engine 12.3.9HF1 - Available
Automation.Engine 21.0.4 - Available

Additional Information

Solution details: A problem has been fixed where a C_PERIOD is stuck in status 'Sleeping' for the rest of the day. This happened only when using 'after the previous execution end plus' option.