Uploaded image for project: 'JITL - JobScheduler Integrated Template Library'
  1. JITL - JobScheduler Integrated Template Library
  2. JITL-564

SystemMonitor Notification generates notification for delay even if the Job chain gets fail before the maximum time of Timer

    XMLWordPrintable

Details

    Description

      Current Situation

      • When a job chain is being monitored by System Monitor and Job Chain contains "On Error" setback, then if the JobChain fails then the SystemMonitor generates two notifications one for the Job chain failure and second for the delay. 
      • Make sure that the START_TIME for the Job chain in both the notifications are different, i.e. the notification of the failure of Job chain includes the START_TIME of the current Job Chain failure, but the delay notification includes the START_TIME of the previous run of Job chain. 

      How to reproduce

      • Unzip the JITL-564.zip to the live folder.
      • Copy the SystemMonitorNotification_MonitorSystem.xml in the {SCHEDULER_DATA}/config/notification folder
      • Run the Job Chain
      • Start the order of the SystemMonitor Job Chain, you will two notifications generated one for the failure and one for the delay.

      Note: The START_TIME for the Job chain in both the notifications are different, i.e. the notification of the failure of Job chain includes the START_TIME of the current Job Chain failure, but the delay notification includes the START_TIME of the previous run of Job chain

      Desired Behavior

      • SystemMonitor Notification should not generate a notification for delay if the Job chain gets fail before the maximum time of Timer, even if the job chain includes setback.

      Attachments

        Activity

          People

            re Robert Ehrlich
            Kanika-Agrawal Kanika Agrawal
            Kanika Agrawal Kanika Agrawal
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: