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.

C_PERIOD runs all tasks but is ENDED_NOT_OK - aborted end status


Article ID: 237372


Updated On:


CA Automic Workload Automation - Automation Engine CA Automic One Automation


When running cyclical tasks (C_PERIOD objects), there are some that end with ENDED_NOT_OK status.  All their child tasks run and the end time appears to be midnight or period turnaround for the object.


Behavior as designed


Release : 12.3.7

Component :


This status of ENDED_NOT_OK is caused by a return code of 1 or 2 for the C_PERIOD object.  See the documentation here

The period container starts tasks according to the settings specified on the Execution <object name> dialog. If it has ended, it waits until all tasks have finished and removes itself from the Tasks window. To see the details on how the tasks have ended, open the Executions lists (see Execution Data), where the following error indicators are provided:

  • 0: All tasks ended successfully.
  • 1: Some task ended abnormally
  • 2: No task ended successfully

The log file of C_PERIOD tasks changes every day when the time frame starts and when the settings are changed. The error indicator is reset when the log file changes.