History of jobs and job chains is not updated in time

Current Situation

• Users observe that the history of jobs and job chains that is available from the JOC Cockpit is not updated in time. Such updates do take place, however, it could take minutes.
• The same applies to the JobScheduler Monitoring Interface that does not receive information about completed job executions in time.
• The reason for this behavior is an optimization added with release 1.11.5 that prevents the plugin from running concurrently in cluster mode. The plugin chooses an interval of 2s before being re-executed. However, if JobScheduler is running in an environment with really powerful machines and a fast database then the previous run of the FactPlugin might take only a few milliseconds and therefore the interval is applied. The synchronization will then be performed with the next changes caused by a job to update the history which happes at an arbitrary point in time.

Desired Behavior

• The FactPlugin should update the history in time and with a delay of not more than 2s.