AAI Performance Issues During Jobstream Add or Rebuild Operations Due to Excessive Run History

Products

• Automation Analytics & Intelligence

Issue/Introduction

Users may experience significant performance degradation, including long wait times or unresponsive behavior, when adding, editing, or rebuilding jobstreams in Automation Analytics & Intelligence (AAI). This behavior is often caused by an excessive default jobstream run history limit, which forces the system to query and process large amounts of historical data during every modification operation.

Environment

• Automation Analytics & Intelligence (AAI)

Cause

The client.jobStreamRunHistoryInitialLimit parameter dictates how many days of job run history AAI retrieves when a new jobstream is created or rebuilt. If this value is set too high (or left at default), the system attempts to load an excessive amount of historical data. Each add or rebuild operation triggers a new query against this entire historical set, consuming database and system resources and causing performance bottlenecks.

Resolution

To improve performance, reduce the initial run history limit by updating the client.jobStreamRunHistoryInitialLimit

1. Update the  client.jobStreamRunHistoryInitialLimit parameter in the AAI Configuration Tool -> Parameters tab
2. Verification: Once the service has restarted, log in to the AAI Web UI and create a new jobstream. In the Jobstream definition dialog, verify that the historical limit setting (often displayed as "Include all historical runs in the last X days") reflects the new value you configured.