Autosys job runs missing from AAI Job Run History

Products

• Automation Analytics & Intelligence

Issue/Introduction

AutoSys is showing job runs for a job that AAI is missing the job runs for.

When checking the AAI database you can see the missing job runs in the JobRun table but the job runs missing from the WebUI do not have an endTime in the database.

 

Environment

AAI 24.x

AutoSys configured for High Availability 

Cause

Database replication latency occasionally spikes, exceeding the default 5-second grace period ․ The Jammer process polls the database, waits 5 seconds, and queries again to catch late events ․ If replication takes longer, the high-water mark advances and permanently misses terminal events like BYPASS ․ Without an end time, the UI filters out the history and leaves the job RUNNING in the AAI databse and only 1 instance of the job will show running in the web UI at a time.

 

Resolution

1․ Update the jammerQueryDelay parameter in the AAI configuration tool to 60 seconds or longer.

Updating through the configuration tool should not require a restart of the AAI service.

 

2. If you cannot access the configuration tool these changes can be made through a direct database update and then a restart of the AAI service.

 

Below is the SQL that can be run:

REPLACE INTO JAWSPROPERTIES (PROPERTYNAME, STRVALUE, INTVALUE) SELECT 'jammerQueryDelay', NULL, 60000 FROM DUAL WHERE NOT EXISTS (SELECT 1 FROM JAWSPROPERTIES WHERE PROPERTYNAME = 'jammerQueryDelay');

COMMIT;

When updating through the database you will need to restart the AAI service for the parameter to be recognized.

 

 

VERIFY SUCCESS:

• Run history populates accurately after a 60-second delay

   

• Jobs transition from RUNNING to terminal states properly