Visualization Issue with C_PERIODs and Child Task Executions in V24

Products

• CA Automic Workload Automation - Automation Engine
• CA Automic One Automation
• Automic SaaS

Issue/Introduction

After upgrading from Automic Automation v21 to v24, users may notice an undocumented change in how Period Containers (C_PERIOD) display child task executions in the Process Monitoring perspective.
When viewing the execution list of a C_PERIOD task that has spanned multiple days or turnarounds:

• Expanding a previous day's execution result shows the subsequent day's C_PERIOD as a nested child task.
• Continuing to expand these nested containers causes the view to "jump" or nest repeatedly (e.g., Day 4 nested under Day 3, which is nested under Day 2).
• This behavior is confusing as it differs from v21, where each C_PERIOD turnaround was displayed as its own top-level container in the execution list.

 

Steps to reproduce:

1) Start a task via Execute Recurring to do something like run 4 times a day (low number simply to simplify the explanation of actual vs expected behavior)
2) Let this run for multiple turnarounds
3) Navigate to Process Monitoring, righ-click the C_PERIOD and choose Executions
4) Expand the second or third C_PERIOD task that shows up in the list

Expected behavior:
In 21, the second C_PERIOD was considered its own container and would expand itself, staying on it's line, so PM would show something like:
C_PERIOD (running)
C_PERIOD (ENDED)
  task in C_PERIOD
  task in C_PERIOD
  etc
  
Actual behavior in 24:
first 
Expand the second one, it immediately "jumps into" the first to something like. 
  C_PERIOD (second)
    CPERIOD (first)
 task in C_PERIOD (second)
 task in C_PERIOD (second)
 etc...

Expand the fourth, it immediately "jumps into" the third, not the list looks like:   
  C_PERIOD (fourth)
    C_PERIOD (third)
    task in C_PERIOD (fourth)
 task in C_PERIOD (fourth)
 etc...

Expand the third and the full thing immediately "jumps" into the second that is in the first. 
  C_PERIOD (third)
    C_PERIOD (fourth)
      C_PERIOD (second)
     C_PERIOD(first)
 task in C_PERIOD (second)
 task in C_PERIOD (second)
 etc...
   task in C_PERIOD (third)
   task in C_PERIOD (third)
   etc...
 task in C_PERIOD (fourth)
 task in C_PERIOD (fourth)

Environment

Version: 24.4.x

Resolution

This issue is purely cosmetic and does not impact the running of C_PERIOD objects or their behavior.

This issue is planned to be fixed with 24.4.4, currently due out in March of 2026.  Please subscribe to this article in order to receive updates.