search cancel

C_PERIOD does not start new task after period change


Article ID: 84860


Updated On:


CA Automic Workload Automation - Automation Engine


Error Message :

A periodic object from 17.01 activated a task and the periodic object was ended by the daily change.

The started task in this case is in activation (in other cases, it may already be started).  The task runs and ends normally.

The newly periodic planned object (after day change, i.e. on 18.01) starts no new tasks.  Instead, it is necessary to manually click on the properties of the task in the activity window and confirm with OK, then the tasks are started.

In some cases around the Period-/Day-change, a periodically planned Object starts no new tasks.  It doesn’t matter which C_PERIOD object, all can be affected.


If you look at the screenshot below. 

  1. 545728801 is started by Parent 545377094 (also see the report shown).
  2. Then the parent C_PERIOD 545377094 was ended.
  3. Now the C_PERIOD 545729696 started no further tasks.
  4. Only the changed 545746100 started everything as expected.

<Please see attached file for image>

Please install one of the updated versions below.


Release: AUTWAB99000-11.0-Automic Workload Automation-Base Edition


Cause type:
Root Cause: Periodic task no longer works after a period log-change. If a mode "GAP" is started at the same time as the period starts a task, based on the timing, the parent of the child task might be wrong & the period is not reset after the child ended.


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


Fix Status: Released

Fix Version(s):
Component: Automation Engine

Automation Engine 12.1.0 - Available
Automation Engine 12.0.3 - Available
Automation Engine 11.2.6 - Available

Additional Information

Workaround :
Restart the C_PERIOD.


1558692664953000084860_sktwi1f5rjvs16lsr.png get_app