Autosys JobstreamRun Not Displaying for Jobs Running Longer Than 48 Hours
Article ID: 439414
Updated On:
Products
Issue/Introduction
When an Autosys job runs continuously for more than 48 hours, the associated JobstreamRun fails to display in the monitoring view. The expected behavior is that active jobs should remain visible and monitored regardless of duration, but the actual behavior results in the jobstream run dropping from view.
Environment
Product: Broadcom Automation Analytics & Intelligence (AAI)
Version: 24.x
Integration: Autosys
Cause
This issue occurs because the projected end time of the jobstream run (either at its start or during execution) falls outside of the configured prediction window (forecastPeriod). When this happens, the jobstream run is placed into an Unknown status.
AAI uses a specific parameter, unknownJobstreamRunLookback (which defaults to 72:00:00, or 72 hours), to determine exactly how long a jobstream run in an Unknown status should be retained in the Monitoring state. If the job runs longer than this lookback period accounts for, it drops out of the active monitoring view.
Resolution
To resolve this issue and ensure long-running Autosys jobs remain visible, you must extend the lookback period parameter.
Please perform the following steps:
Open the AAI Config Tool.
Locate the parameter:
unknownJobstreamRunLookback.Modify the value from its default of 72 hours to 120 hours.
Save the configuration changes and restart the AAI services if prompted by the Config Tool to apply the new setting.
Feedback
