High number of EEM policies causing Jobstream Web UI delays in AAI 24.4.0

Products

• Automation Analytics & Intelligence

Issue/Introduction

Symptoms

After upgrading to AAI version 24.4.0 and performing the post-upgrade EEM migration steps to add BusinessArea and JobstreamV2 policies, users experience severe performance degradation in the Web UI. Specifically:

• The Jobstream Definitions and Jobstream Runs grids take several minutes to load.
• The system appears to hang or become unresponsive during policy evaluation when an EEM user logs in.
• The latency is typically observed when there is a high volume of migrated policies (e.g., 300+ BusinessArea and 300+ JobstreamV2 policies).

Environment

Product: Automic Automation Intelligence (AAI)
Version: 24.4.0
ComponentL EEM

Cause

In version 24.4.0, AAI introduced a more granular security model requiring new policy classes. The migration script converts legacy jobstream policies into both BusinessArea and JobstreamV2 policies.

If a large number of legacy policies existed, the resulting volume of new policies causes a significant overhead. AAI attempts to evaluate every policy frequently to determine user permissions for UI elements, leading to the observed page load delays.

Resolution

This issue has been identified as a defect and is tracked under DE208281. A formal code fix is being developed by Engineering to optimize policy evaluation logic.

Workaround

To restore UI performance immediately, you can significantly reduce the number of policies AAI needs to evaluate by consolidating redundant JobstreamV2 policies:

1. Consolidate JobstreamV2 Policies:

   • In AAI 24.4.0, the "Resources" section on JobstreamV2 policies does not currently provide granular filtering.
   • Rather than having a unique policy for every jobstream, you only need one or two broad JobstreamV2 policies that grant the required permissions (View, Edit, Create, Delete) to your specific user groups.
   • Delete the redundant migrated JobstreamV2 policies.

2. Retain Functional BusinessArea Policies:

   • Continue to use BusinessArea policies if you need to restrict user visibility to specific Business Areas, as these policies are functional for access control.