Handling of start times and end times for workflow executions

Current Situation

• JOC Cockpit should be prepared to handle a situation as explained from the linked article when the start time of orders is newer than the end time.
• This applies to the calculation of average durations for job execution as used with the functionality to check if a job is running longer or shorter than expected.

Desired Behavior

• The JOC Cockpit History Service should be aware of this situation and should add a warning to the JOC Cockpit log file. A situation with unsynchronized system clocks is not considered detrimental, however, users will not find reasonable timestamps in the History.
• The following functions should exclude records that include the start time > end time from the calculation of average duration:
  • Monitor Service: warnings based on warnIfLonger and warnIfShorter job attributes
  • Daily Plan Service: calculation of the expected duration

Test Instructions

• Create and deploy a workflow with a long running job (use e.g. a Shell job with ping -n 60 localhost).
• Start workflow execution.
• Stop JOC Cockpit service (before the workflow execution is finished).
• Find the current order in the database table HISTORY_ORDERS und add for example 1 day to the order START_TIME.
• Find the current job in the database table HISTORY_ORDER_STEPS und add for example 1 day to the job START_TIME.
• Start JOC Cockpit service.
• Find after workflow execution is finished (synchronized by History) a warning in the JOC Cockpit file about the start_time > end_time situation for the given order/job.