Inconsistent job counts when trimming CA7 jobstreams using different methods in AAI
search cancel

Inconsistent job counts when trimming CA7 jobstreams using different methods in AAI

book

Article ID: 432123

calendar_today

Updated On:

Products

Automation Analytics & Intelligence

Issue/Introduction

When you create and trim the same CA7 jobstream using different methods, the resulting job counts are inconsistent For example, creating a jobstream via CLI or Web UI with auto-trimming defaults and adding a trim point later yields massively different job counts compared to specifying the trim point during the initial jobstream creation ․​​​​‌​‍

 

ERROR MESSAGE: "N/A"

SYMPTOMS:

  • CLI script creation followed by Web UI trimming results in incorrect job counts with multiple SCHED IDs

     

     

  • Web UI creation followed by Web UI trimming results in massive job counts that fail to render in the Gantt view

     
  • Creating the jobstream and specifying the trim point simultaneously results in the correct expected job count

     

     

CONTEXT: Occurs when handling large CA7 jobstreams with circular dependencies across different days IMPACT: Prevents reliable automation of jobstream creation and causes Gantt chart rendering failures

 

Environment

AAI 24.3.x

Cause

Product defect DE176816 causes inconsistent trimming behavior when trim points are added after jobstream creation

 

Resolution

1․ UPGRADE AAI SERVER

Path: Broadcom Support Portal Command: Download and install AAI 24․4․0

 

 

EXPECTED: The defect causing inconsistent trimming behavior is resolved NOTE: Defect DE176816 addresses this issue in the 24․4 release

 

2․ WORKAROUND: SPECIFY TRIM POINTS DURING CREATION

Action: When creating the jobstream in the Web UI, specify the trim point at the exact time of creation rather than adding it later

 

EXPECTED: The jobstream contains the correct number of jobs

 

 

3․ WORKAROUND: BREAK CIRCULAR DEPENDENCIES

Action: Trim predecessors-only of the first job in the workflow to effectively make it the starting job

 

EXPECTED: Circular dependencies are broken and the jobstream renders correctly

 

VERIFY SUCCESS:

  • Jobstreams created via CLI and Web UI produce matching job counts when trimmed․

  • Jobstreams open successfully in the Gantt view․