AAI "Start By" deadline calculates for current day instead of next day for midnight-spanning jobstreams

Products

• Automation Analytics & Intelligence

Issue/Introduction

When configuring a jobstream that runs across midnight boundaries (e.g., a process starting at 11:30 PM and finishing at 12:30 AM), setting the "Start By" time to a time after midnight (e.g., 12:30 AM) causes the system to calculate the deadline for the same calendar day as the start of the run, rather than the following day.

Example:

• Job Start: 2026/07/07 11:39 PM
• Intended "Start By": 2026/07/08 12:30 AM
• AAI Calculation: 2026/07/07 12:30 AM (Resulting in an immediate "Late" status or inaccurate metrics as the deadline appears to be in the past).

Environment

AAI 24.4.x 

Cause

This is a current design limitation in the AAI "Start By" logic. While the SLA settings include an "Advanced" override to handle next-day offsets, the "Start By" metric does not currently have a corresponding date offset or override mechanism.

Resolution

This issue has been identified as a candidate for a product enhancement. A Request for Enhancement (RFE) DE208999 has been submitted to Product Management to introduce a date offset or override feature for the "Start By" setting, similar to the existing SLA override functionality.

Workaround: Currently, there is no direct workaround to force the "Start By" metric to the next day