Inconsistent Job Graph Visibility on Machines Page in AAI
search cancel

Inconsistent Job Graph Visibility on Machines Page in AAI

book

Article ID: 436465

calendar_today

Updated On:

Products

Automation Analytics & Intelligence

Issue/Introduction

Users may observe that the Jobs Running graph on the Machines page displays a different number of job execution lines even when viewed within a very short timeframe (e.g., 1–2 minutes apart) for the same machine and date range.

Environment

 

  • Product: Automation Analytics & Intelligence(AAI)

  • Version: 24.4.x

  • Context: Environments with high-frequency, short-duration jobs (runs lasting only a few seconds).

 

Cause

This behavior is primarily due to the dynamic nature of the default "Last 24 hours to Next 24 hours" date filter.

Because this filter acts as a moving window, the start and end points of the graph are recalculated based on the exact system time at the moment the page is rendered. Even a slight shift in the time window (e.g., two minutes) can alter the granularity of the graph's timeline or cause very short job runs to fall between the "pixels" of the rendered time slots if they are near the edge of the calculated window.

Resolution

This is considered normal behavior within AAI when using relative time filters. To ensure a consistent view for auditing or troubleshooting, follow these recommendations:

  • Use Fixed Time Ranges: Instead of using the relative "Last 24 hours" filter, select a Specific Date/Time Range with a fixed start and end point. This prevents the window from shifting when the page is refreshed.

  • Zoom into Granular Windows: For jobs that run for only a few seconds, the 48-hour default view may be too broad to consistently render every execution line. Zooming in on a specific hour will provide a more stable and accurate representation of short-duration runs.

  • Understand the Moving Window: Note that if you access the page at 7:18 PM, the range is 7:18 PM (Yesterday) – 7:18 PM (Tomorrow). Refreshing at 7:20 PM shifts that entire 48-hour block forward by two minutes, which can change which data points are aggregated or displayed in the UI.