AutoSys Workload Automation

 View Only

Job Run Impact - Autosys 11.3.6 SP3

  • 1.  Job Run Impact - Autosys 11.3.6 SP3

    Posted Nov 13, 2019 06:19 AM
    Edited by Sunish Mittal Nov 13, 2019 06:58 AM
    Hi,

    We did some changes in one of the calendar (Future dates were added) in our environment - Autosys 11.3.6 SP3 at 13:02:21.
    On the other hand there was a job A, whose all last predecessor completed at 13:02:23 on same day.
    This job uses the same calendar which we had updated at 13:02:21.

    Somehow, the job did not run & skipped its run window.
    Can anyone suggest the reason behind it? 

    The time shown in autotrack log will be when we clicked on commit (Through WCC) or when the updation process actually completed?

    Below is the pictorial representation of the scenario.

    BOX B didn’t run once the predecessor completed. Need to know why?



    BOX B Jobs missed its run