FactModel Plugin should store the complete job execution history

Current Situation

• The FactModel Plugin stores records for the job execution history in the reporting database.
• This happens - caused by the Master that calls the Plugin - when tasks are started, are terminated or crash without further information. Similarly entries to the job chain history are stored to the database.
• The plugin works based on the reported start time and end time of tasks and stores the latest start time in the reporting_variables table to catch up with future job executions. An error in the plugin makes it store the start time of the current task as the latest start time which results in inaccurate values if tasks, e.g. executed from Agents on different servers do not use perfectly synchronized clocks or if such events arrive with delays.
• As a result of this behavior some tasks are not registered with job execution history.
• This problem is observed for standalone jobs only, it does not occur for jobs executed with job chains.

Desired Behavior

• Check for a way not to rely on timestamps reported by Agents that might be different from the Master servers's clock.

Workaround 1

• Modify standalone jobs to be executed in a job chain.

Workaround 2

• Unzipt the patch patch_for_jitl_474_on_1.12.0-1.12.4.v2.zip to the ./lib/patches directory of the JobScheduler Master and perform a restart.

Maintainer Notes

• This issue is considered a blocker, we therefore provide a patch for download in the next few days.