Job status time and run time do not match

book

Article ID: 195338

calendar_today

Updated On:

Products

CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation Agent CA Workload Automation AE

Issue/Introduction

Job status time and run time do not match. For example we have a job that is scheduled to run at  2:00.

According to job runs log, it ran at 2:00 but the status time (actual time) shows 2:02. 

Environment

Release : 11.3.6

Component : CA Workload Automation AE (AutoSys)

Resolution

After a network problem which had caused a failover to the secondary node,

databases were synchronized and restarted in Full HA mode.

Since the above operation, job status time and run time did not match anymore.

The jobs ran on time as expected but the status time (actual time) showed 2 minutes later.

 

This usually happens when there is a time difference between the nodes or with the database.

However, when we verified the dates were in synch between the Primary, Shadow an TB nodes, with the Agent nodes as well as both Databases, they all showed the same time.

The internal time in AutoSys seemed to be damaged after the failover and database synch and restart.

The recommended solution is to Stop all the AutoSys Services on the Primary, Shadow and TB nodes, then restart in order to address the encountered issue.

Problem resolved by applying the recommended solution. The job status time and run time are now showing the same as expected.