Automic Workload Automation

 View Only
Expand all | Collapse all

Job not running as per schedule in AWA 11.2

  • 1.  Job not running as per schedule in AWA 11.2

    Posted Jun 21, 2020 03:43 AM
    Hi Team,

    We have scheduled a Job : R57CZM03X_LCZM901_ZM_PY_15 in AWA 11.2 to run every Tuesday at 23.30 CET but it is not running. We have checked all parameters and they are correct as well as have saved and checked status of Schedule in Activity window.

    I have tried reexecuting the Schedule also.

    Schedule name : JDEDWARDS_QA_SCHEDULE_V15

    Attaching Last monitor also

    Schedule

    Schedule time


    Last Monitor

    Kindly help on priority.




    ------------------------------
    Regards,
    Mohd Zain Akbar
    ------------------------------


  • 2.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 21, 2020 09:47 PM
    Hi Team,

    A gentle reminder!

    Kindly update on this issue on priority.

    Regards,
    M Zain Akbar





  • 3.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 02:54 AM

    Hello M Zain,

    IMO, the attached screens might not be all to conclude the exact issues. 

    Did you check the statistics of the schedule object ? Does it execute other objects ? If not then your schedule might be having issue. 
    => Go to statistics of the schedule object => Right click on the current instance => Details => check the last message field for some info there. 

    I see your job had a calendar condition. Is the job not running everyday OR it is not running at all ? 
    => Please check the calendar condition & validate if the day selection matches the execution day. 
    => Check the statistics of the job itself. If the job statistics says ended_inactive then => Edit the job => go to header tab => Check the active check box. 
    => If the case is like the job is running but it is running at a different time => Edit the schedule & verify if you have any timezone object attached there. 

    I hope these help. 



    ------------------------------
    Regards,
    Prosenjit
    ------------------------------



  • 4.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 03:24 AM
    Hi Prosenjit,

    This is a new StandAlone Job created and has been set up with a new schedule that is to run every week on Tuesday at 23.30 CET. I have checked all the calendar conditions,Active status and all are in OK Status. When i tried to save the schedule it gave me the message that Active instances will reload after a period turnaround of 00.00 CET. Please find last message.

    image.png

    Kindly check and investigate.

    Regards,
    M Zain Akbar






  • 5.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 03:31 AM
    Hi Prosenjit,

    To add more here the other schedules are running correctly so when i save the Schedule is it that should i select : Yes on "Active instances will reload after a period turnaround of 00.00 CET."

    Regards,
    M Zain Akbar






  • 6.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 04:53 AM
    Hello M Zain,

    Do you see any "Active" instance of your schedule ( in statistics ) ? I dont see that in your screenshot. The one instance you selected that already ENDED_OK. So it wont be turned around anymore. 

    Your schedule should be in "Active" in execution & Activity window. If not please execute the schedule.

    ------------------------------
    Regards,
    Prosenjit
    ------------------------------



  • 7.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 05:02 AM
    Hi Prosenjit,

    Yes the schedule is in Active State i have given you the last run Screenshot.

    Regards,
    Mohd Zain Akbar






  • 8.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 05:16 AM
    Hi M Zain,

    If that is the case, I am not sure what could go wrong. Possibly somebody from this forum could guide better. Thanks.

    ------------------------------
    Regards,
    Prosenjit
    ------------------------------



  • 9.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 10:49 AM
    Edited by Pete Wirfs Jun 22, 2020 10:50 AM
    Some of your JSCH tasks show "A|C" for their conditions.  I'm pretty sure the "A" indicates that this task has been set "Inactive".  This is a setting in the properties of that task.

    https://docs.automic.com/documentation/webhelp/english/ALL/components/AE/11/All%20Guides/help.htm#ucaaiv.htm%3FTocPath%3DUser%2520Guide%7CObjects%7CAlphabetical%2520Listing%7CSchedule%7CSchedule%2520Tab%7C_____1

    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------



  • 10.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 11:04 AM
    Hi Peter,

    The schedule is active and A|C means here if calendar has been set or with certain conditions whereas in this schedule only one condition is set.

    Kindly assist.

    Regards,
    Mohd Zain Akbar






  • 11.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 11:13 AM
    https://docs.automic.com/documentation/webhelp/english/ALL/components/AE/11/All%20Guides/help.htm#ucaaiv.htm%3FTocPath%3DUser%2520Guide%7CObjects%7CAlphabetical%2520Listing%7CSchedule%7CSchedule%2520Tab%7C_____1

    JSCH help information


    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------



  • 12.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 11:17 AM
    I see that the job you care about does not have the A|C setting.  Therefore I can think of no reason for it to not be kicking off.

    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------



  • 13.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 11:19 AM
    Did the job get renamed by any chance?

    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------



  • 14.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 11:22 AM
    Hi Pete,

    This job has been duplicated from a previous job and certain attributes have been changed but has not been renamed.

    Regards,
    Mohd Zain Akbar






  • 15.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 11:30 AM
    When you check the run history of R57CZM03X_LCZM901_ZM_PY_15, is there any record of it having tried to run at the desired time?

    If there is record of it having tried to run at the desired time, then you should be able to find diagnostic messages in that run history that will tell you why it did not work.

    If there is no record of it having tried to run at the desired time, then the focus must be put upon the JSCH object, and you will need to check the JSCH run history for diagnostic messages.

    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------



  • 16.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 11:34 AM
    Hi Pete,

    The job has not run at all as per it's schedule.

    Regards,
    Mohd Zain Akbar






  • 17.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 11:38 AM
    Then your next step is to investigate the JSCH object's run history.  Open the monitor for the prior days run, and see what messages are associated with the job that failed to launch.

    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------



  • 18.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 22, 2020 11:38 PM
    Hi Pete,

    Please find attached the last run Logs of The Job Schedule: "JDEDWARDS_QA_SCHEDULE_V15"

    2020-06-23 00:00:50 - U00011089 Task 'JDE_ADDRESS_BOOK_WORD_SEARCH_2_QA_V15' starting ...
    2020-06-23 00:00:50 - U00011094 Task 'JDE_MONTHLY_INVENTORY_ZAMBIA_QA_V15' is not activated due to the specified Calendar settings.
    2020-06-23 00:00:50 - U00011089 Task 'JDE_P2P_DAY_BATCH_SA001_PD_QA_V15' starting ...
    2020-06-23 00:00:50 - U00011089 Task 'JDE_P2P_NIGHT_BATCH_SAUDI_QA_V15' starting ...
    2020-06-23 00:00:50 - U00011089 Task 'JDE_P2P_NIGHT_BATCH_SYRIA_QA_V15' starting ...
    2020-06-23 00:00:50 - U00011087 Task 'PENDING_EXPENSE_REPORT_MAIL_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 00:00:50 - U00011089 Task 'R56B4210_LBDZ901_DZ_PY_V15' starting ...
    2020-06-23 00:01:01 - U00011090 Task 'R56B4210_LBDZ901_DZ_PY_V15' is now active (RunID '0036546215').
    2020-06-23 00:01:09 - U00011089 Task 'JDE_R57CZM05_ZM_PY_V15.JOBP' starting ...
    2020-06-23 00:01:10 - U00011090 Task 'JDE_P2P_DAY_BATCH_SA001_PD_QA_V15' is now active (RunID '0036543855').
    2020-06-23 00:01:09 - U00011090 Task 'JDE_P2P_NIGHT_BATCH_SAUDI_QA_V15' is now active (RunID '0036545234').
    2020-06-23 00:01:10 - U00011090 Task 'JDE_ADDRESS_BOOK_WORD_SEARCH_2_QA_V15' is now active (RunID '0036547046').
    2020-06-23 00:01:10 - U00011090 Task 'JDE_P2P_NIGHT_BATCH_SYRIA_QA_V15' is now active (RunID '0036543856').
    2020-06-23 00:01:15 - U00011090 Task 'JDE_R57CZM05_ZM_PY_V15.JOBP' is now active (RunID '0036543905').
    2020-06-23 00:01:29 - U00011091 Task 'JDE_P2P_NIGHT_BATCH_SAUDI_QA_V15' (RunID '0036545234') ended.
    2020-06-23 00:01:31 - U00011091 Task 'JDE_P2P_NIGHT_BATCH_SYRIA_QA_V15' (RunID '0036543856') ended.
    2020-06-23 00:02:30 - U00011091 Task 'JDE_P2P_DAY_BATCH_SA001_PD_QA_V15' (RunID '0036543855') ended.
    2020-06-23 00:03:00 - U00011091 Task 'R56B4210_LBDZ901_DZ_PY_V15' (RunID '0036546215') ended.
    2020-06-23 00:03:30 - U00011091 Task 'JDE_R57CZM05_ZM_PY_V15.JOBP' (RunID '0036543905') ended.
    2020-06-23 00:30:10 - U00011089 Task 'MMN_CONSULTANT_ERP_QA_V15' starting ...
    2020-06-23 00:30:19 - U00011090 Task 'MMN_CONSULTANT_ERP_QA_V15' is now active (RunID '0036546352').
    2020-06-23 01:00:10 - U00011089 Task 'GC_CHANGE_STATUS_CONSUMPTIONS_V15' starting ...
    2020-06-23 01:00:10 - U00011089 Task 'JDE_CAMEROON_SCHEDULER_JOB_CM_QA_V15' starting ...
    2020-06-23 01:00:10 - U00011087 Task 'JDE_DAILY_MONTOFRIDAY_FIN_HU_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 01:00:10 - U00011087 Task 'JDE_DAILY_MONTOFRIDAY_P2P_HU_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 01:00:10 - U00011089 Task 'JDE_EFFECTIVE_ADDRESS_UPDATE_QA_V15' starting ...
    2020-06-23 01:00:10 - U00011087 Task 'JDE_EFFE_ADDRESS_UPDATE_HU_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 01:00:10 - U00011089 Task 'JDE_PUR_P2PREDESIGN_DMAAI_UPLO_QA_V15' starting ...
    2020-06-23 01:00:10 - U00011089 Task 'JDE_SQL_DELETE_F00095_ZM_QA_V15' starting ...
    2020-06-23 01:00:13 - U00011090 Task 'GC_CHANGE_STATUS_CONSUMPTIONS_V15' is now active (RunID '0036545358').
    2020-06-23 01:00:14 - U00011090 Task 'JDE_SQL_DELETE_F00095_ZM_QA_V15' is now active (RunID '0036545360').
    2020-06-23 01:00:24 - U00011090 Task 'JDE_CAMEROON_SCHEDULER_JOB_CM_QA_V15' is now active (RunID '0036547172').
    2020-06-23 01:00:25 - U00011090 Task 'JDE_PUR_P2PREDESIGN_DMAAI_UPLO_QA_V15' is now active (RunID '0036547173').
    2020-06-23 01:00:25 - U00011090 Task 'JDE_EFFECTIVE_ADDRESS_UPDATE_QA_V15' is now active (RunID '0036545359').
    2020-06-23 01:00:29 - U00011091 Task 'JDE_SQL_DELETE_F00095_ZM_QA_V15' (RunID '0036545360') ended.
    2020-06-23 01:00:31 - U00011091 Task 'GC_CHANGE_STATUS_CONSUMPTIONS_V15' (RunID '0036545358') ended.
    2020-06-23 01:01:30 - U00011091 Task 'JDE_EFFECTIVE_ADDRESS_UPDATE_QA_V15' (RunID '0036545359') ended.
    2020-06-23 01:11:00 - U00011091 Task 'JDE_CAMEROON_SCHEDULER_JOB_CM_QA_V15' (RunID '0036547172') ended.
    2020-06-23 01:30:10 - U00011094 Task 'JDE_INVENTORY_SA_JFRPD_QA_V15' is not activated due to the specified Calendar settings.
    2020-06-23 01:30:10 - U00011089 Task 'JDE_INVENTORY_TU_TO_FRI_JFRPD_QA_V15' starting ...
    2020-06-23 01:30:10 - U00011089 Task 'JDE_P2P_P2PREDESIGN_DMAAI_UPL_ZM_QA_V15' starting ...
    2020-06-23 01:30:18 - U00011090 Task 'JDE_P2P_P2PREDESIGN_DMAAI_UPL_ZM_QA_V15' is now active (RunID '0036547248').
    2020-06-23 01:30:19 - U00011090 Task 'JDE_INVENTORY_TU_TO_FRI_JFRPD_QA_V15' is now active (RunID '0036548073').
    2020-06-23 01:31:30 - U00011091 Task 'JDE_P2P_P2PREDESIGN_DMAAI_UPL_ZM_QA_V15' (RunID '0036547248') ended.
    2020-06-23 02:00:10 - U00011087 Task 'JDE_CUSTOM_ACTIVITY_LOG_UPDATE_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 02:00:10 - U00011087 Task 'JDE_DUE_AMOUNT_UPDATE_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 02:00:10 - U00011094 Task 'JDE_INTERCO_CONCRETE_AGREGATE_PO_RECEIPT_AND_MATCH_DRIVER_QA_V15' is not activated due to the specified Calendar settings.
    2020-06-23 02:10:01 - U00011091 Task 'MMN_CONSULTANT_ERP_QA_V15' (RunID '0036546352') ended.
    2020-06-23 02:42:31 - U00011091 Task 'JDE_PUR_P2PREDESIGN_DMAAI_UPLO_QA_V15' (RunID '0036547173') ended.
    2020-06-23 02:49:01 - U00011091 Task 'JDE_INVENTORY_TU_TO_FRI_JFRPD_QA_V15' (RunID '0036548073') ended.
    2020-06-23 04:00:00 - U00011087 Task 'JDE_GL_POSTINGS_AND_RELATED_GBC_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 04:00:00 - U00011087 Task 'JDE_GL_POSTINGS_AND_RELATED_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 04:00:00 - U00011089 Task 'JDE_P2P_ITEMASOF_RUNUBE_JDZPD_QA_V15' starting ...
    2020-06-23 04:00:00 - U00011087 Task 'JDE_ZM_REPRICE_VAT_LINE_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 04:00:09 - U00011090 Task 'JDE_P2P_ITEMASOF_RUNUBE_JDZPD_QA_V15' is now active (RunID '0036547538').
    2020-06-23 04:01:31 - U00011091 Task 'JDE_P2P_ITEMASOF_RUNUBE_JDZPD_QA_V15' (RunID '0036547538') ended.
    2020-06-23 04:30:01 - U00011094 Task 'JDE_INTCO_RECEIPT_MATCH_DRIVER_QA_V15' is not activated due to the specified Calendar settings.
    2020-06-23 04:33:01 - U00011094 Task 'JDE_PURCH_TRANSPSERVICES_LC_QA_V15' is not activated due to the specified Calendar settings.
    2020-06-23 04:43:01 - U00011091 Task 'JDE_ADDRESS_BOOK_WORD_SEARCH_2_QA_V15' (RunID '0036547046') ended.
    2020-06-23 05:00:02 - U00011089 Task 'JDE_ACA_POSTING_QUANTITIES_QA_V15' starting ...
    2020-06-23 05:00:02 - U00011089 Task 'JDE_AR_ANALYTICAL_2_REPORTS_GC_QA_V15' starting ...
    2020-06-23 05:00:02 - U00011089 Task 'JDE_AR_ANALYTICAL_REPORT_GC_QA_V15' starting ...
    2020-06-23 05:00:02 - U00011094 Task 'JDE_INTEGRITY_REPORTS_CM_AP_PY_V15' is not activated due to the specified Calendar settings.
    2020-06-23 05:00:02 - U00011094 Task 'JDE_INTEGRITY_REPORTS_CM_AR_PY_V15' is not activated due to the specified Calendar settings.
    2020-06-23 05:00:02 - U00011094 Task 'JDE_INTEGRITY_REPORTS_CM_FA_PY_V15' is not activated due to the specified Calendar settings.
    2020-06-23 05:00:02 - U00011094 Task 'JDE_INTEGRITY_REPORTS_CM_GL_PY_V15' is not activated due to the specified Calendar settings.
    2020-06-23 05:00:02 - U00011094 Task 'JDE_INTEGRITY_REPORTS_CM_P2P_PY_V15' is not activated due to the specified Calendar settings.
    2020-06-23 05:00:02 - U00011087 Task 'JDE_INTEGRITY_TESTS_GBC_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 05:00:02 - U00011087 Task 'JDE_INTEGRITY_TESTS_GBC_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 05:00:02 - U00011087 Task 'JDE_INTEGRITY_TESTS_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 05:00:02 - U00011087 Task 'JDE_INTEGRITY_TESTS_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 05:00:12 - U00011090 Task 'JDE_ACA_POSTING_QUANTITIES_QA_V15' is now active (RunID '0036547649').
    2020-06-23 05:00:15 - U00011091 Task 'JDE_ACA_POSTING_QUANTITIES_QA_V15' (RunID '0036547649') ended.
    2020-06-23 05:00:15 - U00011090 Task 'JDE_AR_ANALYTICAL_REPORT_GC_QA_V15' is now active (RunID '0036547650').
    2020-06-23 05:00:17 - U00011090 Task 'JDE_AR_ANALYTICAL_2_REPORTS_GC_QA_V15' is now active (RunID '0036545789').
    2020-06-23 05:05:02 - U00011091 Task 'JDE_AR_ANALYTICAL_REPORT_GC_QA_V15' (RunID '0036547650') ended.
    2020-06-23 05:15:02 - U00011087 Task 'JDE_POST_GL_BATCHES_GBC_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 05:15:02 - U00011087 Task 'JDE_POST_GL_BATCHES_QA_V15' will not be activated (indicated by active identifier).
    2020-06-23 05:15:02 - U00011091 Task 'JDE_AR_ANALYTICAL_2_REPORTS_GC_QA_V15' (RunID '0036545789') ended.
    2020-06-23 05:30:04 - U00011089 Task 'JDE_GL_ACA_POSTINGS_QA_V15' starting ...
    2020-06-23 05:30:04 - U00011089 Task 'JDE_POSTINGS_AND_SALES_UPDATES_QA_V15' starting ...
    2020-06-23 05:30:04 - U00011094 Task 'LAUNCH_SCHEDULED_FOR_FNP_QA_V15' is not activated due to the specified Calendar settings.
    2020-06-23 05:30:04 - U00010016 Activation of 'JDE_GL_ACA_POSTINGS_QA_V15' was aborted. Object is set inactive.
    2020-06-23 05:30:04 - U00011091 Task 'JDE_GL_ACA_POSTINGS_QA_V15' (RunID '0036549333') ended.
    2020-06-23 05:30:04 - U00010016 Activation of 'JDE_POSTINGS_AND_SALES_UPDATES_QA_V15' was aborted. Object is set inactive.
    2020-06-23 05:30:04 - U00011091 Task 'JDE_POSTINGS_AND_SALES_UPDATES_QA_V15' (RunID '0036545880') ended.


    Regards,
    M Zain Akbar






  • 19.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 23, 2020 09:31 AM
    Hi M Zain, Can you try this ? 

    #A : Edit the Schedule => Go to header tab => Check the current version of the schedule. 
    #B : Now go to the statistics of the schedule => Check the available version column. 

    Does the version number gets matched #A vs #B ? ​​​​

    If these do not match then, the running instance did not take latest change into the consideration. Then QUIT the schedule & Execute the schedule again. 
    If these 2 versions got matched then your issue is not related to ScheduleReload, but somewhere else.

    ------------------------------
    Regards,
    Prosenjit
    ------------------------------



  • 20.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 23, 2020 10:21 AM
    Hi Prosenjit,

    Kindly confirm "QUIT" means deactivating the schedule and reactivating it again and then executing it.

    Regards,
    Mohd Zain Akbar






  • 21.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 23, 2020 11:14 AM
    Hi Prosenjit,

    Kindly find the details regarding the version:

    image.png

    image.png

    image.png
    Regards,
    M Zain Akbar







  • 22.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 23, 2020 11:18 AM
    Hi Prosenjit,

    Kindly reply on priority as we have an activity planned today.

    Regards,
    Mohd Zain Akbar






  • 23.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 23, 2020 12:16 PM
    Hi M Zain,

    Now I see the problem. The currently ACTIVE instance is of version 128. QUIT this instance. Then EXECUTE a fresh instance of your schedule. 


    ------------------------------
    Regards,
    Prosenjit
    ------------------------------



  • 24.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 23, 2020 01:25 PM
    Edited by Pete Wirfs Jun 23, 2020 01:29 PM
    I agree with Prosenjit.  You are currently executing version 130 of your JSCH object, but you want to be executing version 131 of your JSCH object.  To accomplish this you must QUIT the one that is running (or "deactivate", if you prefer to call it that.) and then execute it.

    This is not without risk however.  If staff at your installation are in a habit of modifying the currently-running JSCH (this can be done via the monitor of the executing instance), those modifications will be lost.

    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------



  • 25.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 23, 2020 02:36 PM
    Hi Pete/Prosenjit,

    I have done the steps that you have mentioned but in the Monitor section i am unable to see the expected Job run of the Job as mentioned in the Schedule. 

    image.png

    image.png

    Should i wait for the Scheduled time if the Job runs or not.

    Regards,
    M Zain akbar






  • 26.  RE: Job not running as per schedule in AWA 11.2

    Posted Jun 23, 2020 05:00 PM
    It looks to me like it should not run until 23:30 tonight.

    I also see a "C" condition rule on it.  This means it has a calendar rule on the task that will probably make it skip on certain days.

    ------------------------------
    Pete Wirfs
    SAIF Corporation
    Salem Oregon USA
    ------------------------------



  • 27.  RE: Job not running as per schedule in AWA 11.2
    Best Answer

    Posted Jun 23, 2020 09:51 PM
    Edited by Christopher Hackett Jun 25, 2020 03:52 PM
    Hello M Zain,

    I have a doubt that your schedule is actually running properly as I see all those child task items in preparing state.

    They all should be mostly in Ended_Inactive due to definition / Ended_Inactive due to calendar / Start time exceeded / Active / waiting for start time.   

    I saw one of your earlier references, the instance was 'Start Impossible'. Are you sure the Last Monitor you gave in screenshot is actually Active ?

    If it is active then you need to wait for the time & as Pete said, depending on the Calendar Conditions it will run OR will not run on a particular day.

    The other thing I would ask you to do is - Whenever you make any change to the schedule, make a practice of following -

    - Watch the last monitor find out 1 min / 2 min clean window ( no jobs during that time )
    - QUIT the schedule & Execute it immediately. 

    Above has many advantages including this scenario that we are discussing here. Some of the advantages are following - 
    - While you edit the object & save, it says "Do you want to reflect the changes at next turnaround time" - sometimes performer selects 'no' by mistake. If you follow above method you don't need to remember that turnaround time anymore. Your change will be effective immediately. 

    - Lets say current time is 10:00 AM & you added one object which should run at 10:15 AM. Now if you wait for turnaround time it might not be executed by the current schedule instance due to versioning. If you follow above process, your every change will be picked up by the latest execution.  

    - Only one WARNING on this - be watchful with the instances modified on runtime of Schedule Monitor.

    ------------------------------
    Regards,
    Prosenjit
    ------------------------------