In the Web UI, running jobstreams may display "No Data" for the predicted End Time ․
ERROR MESSAGE:
"The jobstream run you are looking at has become invalid because the jobstream definition has been modified․
Please click the following link to navigate to another page․"
SYMPTOMS:
Jobstream main screen shows predicted end time as blank or "No Data"
Clicking the link for the job run displays "unknown"
Following the job link yields the invalid jobstream definition error
CONTEXT: Occurs when monitoring running jobstreams in the Web UI
IMPACT: Users cannot accurately predict when jobstreams will complete
Automation Analytics & Intelligence (AAI) 24․X
The predicted end time fails to calculate when the job start and end times are exactly the same, or when the jobstream definition is modified without correctly trimming repetitive jobs ․
STEPS:
1․ ENABLE JOBSTREAM START JOBS
Path: Configuration Tool -> Params Set client․enableJobstreamStartJobs to true (disabled by default)
Note: This does not require a restart just a closing of the WebUI and opening again.
EXPECTED: The Start tab becomes visible when editing jobstreams in the Web UI
NOTE: This is an advanced feature and should be used with care
2․ CONFIGURE THE START JOB
Path: Web UI -> Edit Jobstream -> Start Tab Select and set the appropriate start job for the [jobstream-name] jobstream
EXPECTED: The target job [start-job-name] is assigned
WARNING: Alerts will be removed when doing this․ Set the rebuild data date to recreate history if needed
3․ ADJUST AUTO TRIM VALUES
Path: Web UI -> Edit Jobstream -> Auto Trim Tab. Ensure Auto Trim is enabled. Review the Repetitive jobs value․
If run frequencies are higher than the current setting, increase the value (the default is 1․5)
EXPECTED: Jobstream successfully trims repetitive jobs and correctly predicts end times
VERIFY SUCCESS:
Monitor the jobstream during its next run to confirm the predicted end time populates correctly
Verify that no invalid jobstream errors appear when clicking job runs
PREVENTION: Ensure Auto Trim is configured correctly for jobstreams with high run frequencies ․