Exceeded SLA Alerts generated at unexpected times for AutoSys jobstreams in AAI Due to "Allow new run based on Force started job" Setting

Products

• Automation Analytics & Intelligence

Issue/Introduction

Customers may observe inconsistent alerting behavior for jobstreams, specifically:

• Not Predicted to Finish (NPTF) alerts firing at unexpected times or not at all.
• Exceeded Deadline (formerly Exceeded SLA) alerts firing significantly later than the actual deadline breach.

Environment

• AAI integrated with AutoSys schedulers.
• Jobstreams where manual "force starts" are part of the operational workflow.

Cause

The issue is typically caused by the jobstream configuration setting "Allow new run based on Force started job" being enabled.

When this setting is active:

1. AAI creates a new, separate jobstream run whenever a sendevent issues a force start on a job within the hierarchy.
2. Multiple active runs for the same jobstream can exist simultaneously.
3. AAI may evaluate alerts against a "stale" or secondary run rather than the primary batch execution, leading to suppressed or delayed notifications for the actual production path.

Resolution

To ensure stable and predictable SLA alerting, disable the force-start run setting:

1. Open the AAI Thick Client or Web UI.
2. Locate and Edit the impacted Jobstream.
3. Navigate to the Hierarchy tab.
4. Uncheck the box for "Allow new run based on Force started job".
5. Click OK/Save.